Building data platform with a distributed digital twin

ABSTRACT

A method including receiving, by one or more processing circuits, building data, generating, by the one or more processing circuits, a first digital twin based on the building data, wherein a first system stores the first digital twin and a second system stores a second digital twin generated based on the building data, where the first digital twin includes a relationship that forms a connection between the first digital twin and the second digital twin by linking a first entity of the first entities of the first digital twin and a second entity of the second entities of the second digital twin, and performing, by the one or more processing circuits, one or more operations based on at least one of the first digital twin, the second digital twin, or the relationship that forms the connection between the first digital twin and the second digital twin.

CROSS-REFERENCE TO RELATED PATENT APPLICATION

This application is a continuation of U.S. patent application Ser. No.17/534,821 filed Nov. 24, 2021, the entirety of which is incorporated byreference herein.

BACKGROUND

The present disclosure relates generally to the management of buildingsystems and devices of a building. The present disclosure relates moreparticularly to managing information of building systems and controllingthe building systems.

A building can include various types of building subsystems, e.g.,heating, ventilation, and air conditioning (HVAC) systems, securitysystems, fire response systems, access control systems, etc. In somecases, a central cloud system may manage the information of the varioussystems and control the various systems of the building. However, insome cases, local computing resources may be able to provide betterreal-time management of systems of a building. However, it may bedifficult to manage the storage of information and operationalresponsibilities across local computing resources and cloud computingresources.

SUMMARY

One implementation of the present disclosure is a method includingreceiving, by one or more processing circuits, at least a portion ofbuilding data describing entities of a building and relationshipsbetween the entities, the entities represent at least one of a device, aspace, the building, a point, or a person. The method includesgenerating, by the one or more processing circuits, a first digital twinbased on the building data, wherein a first system stores the firstdigital twin and a second system stores a second digital twin generatedbased on the building data. The first digital twin includes firstentities of the entities and first relationships of the relationshipsbetween the first entities, wherein the second digital twin includessecond entities of the entities and second relationships of therelationships between the second entities, wherein the first digitaltwin includes a relationship that forms a connection between the firstdigital twin and the second digital twin by linking a first entity ofthe first entities of the first digital twin and a second entity of thesecond entities of the second digital twin. The method includesperforming, by the one or more processing circuits, one or moreoperations based on at least one of the first digital twin, the seconddigital twin, or the relationship that forms the connection between thefirst digital twin and the second digital twin.

In some embodiments, the first system and the second system are at leastone of a cloud system stored off premises from the building or an edgesystem stored on a premises of the building.

In some embodiments, the one or more processing circuits include atleast one of a first processing circuit of the first system or a secondprocessing circuit of the second system.

In some embodiments, the one or more processing circuits include aprocessing circuit of the first system. In some embodiments, performingthe one or more operations includes executing, by the processing circuitof the first system, an agent stored by the first system, the agentconfigured to perform the one or more operations based on the firstdigital twin and ingesting, by the agent, a result of the one or moreoperations into the first digital twin.

In some embodiments, the second digital twin includes a secondrelationship that forms another connection between the second digitaltwin and the first digital twin by linking the second entity of thesecond entities of the second digital twin and the first entity of thefirst entities of the first digital twin.

In some embodiments, the one or more processing circuits include a firstprocessing circuit of the first system and a second processing circuitof the second system. In some embodiments, the method includesperforming an onboarding to generate the first digital twin and thesecond digital twin by receiving, by the first processing circuit of thefirst system, first building data of the building data, generating, bythe first processing circuit of the first system, the first digital twinbased on the first building data, receiving, by the second processingcircuit of the second system, second building data of the building data,generating, by the second processing circuit of the second system, thesecond digital twin based on the second data, identifying, by the firstprocessing circuit of the first system, the relationship that forms theconnection between the first digital twin and the second digital twin bycommunicating with the second system, and causing, by the firstprocessing circuit of the first system, the first digital twin toinclude the relationship.

In some embodiments, the first digital twin includes a first graphstructure including first nodes representing the first entities andfirst edges between the first nodes representing the first relationshipsbetween the first entities. In some embodiments, the second digital twinincludes a second graph structure including second nodes representingthe second entities and second edges between the second nodesrepresenting the second relationships between the second entities.

In some embodiments, the first graph structure includes a nodeidentifying the second graph structure. In some embodiments, the firstgraph structure includes an edge between a first node of the first nodesrepresenting the first entity and the node identifying the second graphstructure, wherein the edge represents the relationship between thefirst entity of the first entities of the first digital twin and thesecond entity of the second entities of the second digital twin.

In some embodiments, the edge includes data including a first indicationof the first entity, a second indication that the first entity is storedby the first graph structure, a third indication of the second entity, afourth indication that the second entity is stored by the second graphstructure, and a fifth indication of a relationship type of relationshiptypes describing the relationship between the first entity of the firstentities of the first digital twin and the second entity of the secondentities of the second digital twin.

In some embodiments, the one or more processing circuits include aprocessing circuit of the first system. In some embodiments, performingthe one or more operations includes querying, by the processing circuitof the first system, the first digital twin based on a query,identifying, by the processing circuit of the first system, that a queryresult of the query is stored in the second digital twin based on therelationship that forms the connection between the first digital twinand the second digital twin, communicating, by the processing circuit ofthe first system, the query to the second system, receiving, by theprocessing circuit of the first system, the query result, wherein thequery result is based on the second system querying the second digitaltwin based on the query, and performing, by the processing circuit ofthe first system, the one or more operations based on the query result.

In some embodiments, the one or more processing circuits include asecond processing circuit of the second system. In some embodiments, themethod includes receiving, by the second processing circuit of thesecond system, the query from the processing circuit of the firstsystem, querying, by the second processing circuit of the second system,the second digital twin with the query to generate the query result, andcommunicating, by the second processing circuit of the first system, thequery result to the processing circuit of the first system.

In some embodiments, the method includes identifying, by the processingcircuit of the first system, that the second system stores the seconddigital twin based on a lookup table. In some embodiments, the lookuptable stores indications of digital twins including the first digitaltwin and the second digital twin and links between the digital twins andsystems that store the digital twins, the systems including the firstsystem and the second system.

Another implementation of the present disclosure is a system includingone or more memory devices storing instructions thereon that, whenexecuted by one or more processors, cause the one or more processors toreceive at least a portion of building data describing entities of abuilding and relationships between the entities, the entities representat least one of a device, a space, the building, a point, or a person.The instructions cause the one or more processors to generate a firstdigital twin based on the building data, wherein the system stores thefirst digital twin and a second system stores a second digital twingenerated based on the building data, wherein the first digital twinincludes first entities of the entities and first relationships of therelationships between the first entities, wherein the second digitaltwin includes second entities of the entities and second relationshipsof the relationships between the second entities, wherein the firstdigital twin includes a relationship that forms a connection between thefirst digital twin and the second digital twin by linking a first entityof the first entities of the first digital twin and a second entity ofthe second entities of the second digital twin. The instructions causethe one or more processors to perform one or more operations based on atleast one of the first digital twin, the second digital twin, or therelationship that forms the connection between the first digital twinand the second digital twin.

In some embodiments, the system and the second system are at least oneof a cloud system stored off premises from the building or an edgesystem stored on a premises of the building.

In some embodiments, the instructions cause the one or more processorsto execute an agent stored by the first system, the agent configured toperform the one or more operations based on the first digital twin andingest a result of the one or more operations into the first digitaltwin.

In some embodiments, the second digital twin includes a secondrelationship that forms another connection between the second digitaltwin and the first digital twin by linking the second entity of thesecond entities of the second digital twin and the first entity of thefirst entities of the first digital twin.

In some embodiments, the first digital twin includes a first graphstructure including first nodes representing the first entities andfirst edges between the first nodes representing the first relationshipsbetween the first entities. In some embodiments, the second digital twinincludes a second graph structure including second nodes representingthe second entities and second edges between the second nodesrepresenting the second relationships between the second entities.

In some embodiments, the instructions cause the one or more processorsto query the first digital twin based on a query, identify that a queryresult of the query is stored in the second digital twin based on therelationship that forms the connection between the first digital twinand the second digital twin, communicate the query to the second system;receive the query result, wherein the query result is based on thesecond system querying the second digital twin based on the query, andperform the one or more operations based on the query result.

Another implementation of the present disclosure is one or more computerreadable medium storing instructions thereon that, when executed by oneor more processors, cause the one or more processors to receive at leasta portion of building data describing entities of a building andrelationships between the entities, the entities represent at least oneof a device, a space, the building, a point, or a person. Theinstructions cause the one or more processors to generate a firstdigital twin based on the building data, wherein a first system storesthe first digital twin and a second system stores a second digital twingenerated based on the building data, wherein the first digital twinincludes first entities of the entities and first relationships of therelationships between the first entities, wherein the second digitaltwin includes second entities of the entities and second relationshipsof the relationships between the second entities, wherein the firstdigital twin includes a relationship that forms a connection between thefirst digital twin and the second digital twin by linking a first entityof the first entities of the first digital twin and a second entity ofthe second entities of the second digital twin. The instructions causethe one or more processors to perform one or more operations based on atleast one of the first digital twin, the second digital twin, or therelationship that forms the connection between the first digital twinand the second digital twin.

In some embodiments, the first digital twin includes a first graphstructure including first nodes representing the first entities andfirst edges between the first nodes representing the first relationshipsbetween the first entities. In some embodiments, the second digital twinincludes a second graph structure including second nodes representingthe second entities and second edges between the second nodesrepresenting the second relationships between the second entities.

In some embodiments, the instructions cause the first system to performone or more particular operations based on data received from the secondsystem, the data based on the second digital twin, identify acommunication issue between the first system and the second system, andperform the one or more particular operations based on second datadetermined based on the first digital twin.

BRIEF DESCRIPTION OF THE DRAWINGS

Various objects, aspects, features, and advantages of the disclosurewill become more apparent and better understood by referring to thedetailed description taken in conjunction with the accompanyingdrawings, in which like reference characters identify correspondingelements throughout. In the drawings, like reference numbers generallyindicate identical, functionally similar, and/or structurally similarelements.

FIG. 1 is a block diagram of a building data platform including an edgeplatform, a cloud platform, and a twin manager, according to anexemplary embodiment.

FIG. 2 is a graph projection of the twin manager of FIG. 1 includingapplication programming interface (API) data, capability data, policydata, and services, according to an exemplary embodiment.

FIG. 3 is another graph projection of the twin manager of FIG. 1including application programming interface (API) data, capability data,policy data, and services, according to an exemplary embodiment.

FIG. 4 is a graph projection of the twin manager of FIG. 1 includingequipment and capability data for the equipment, according to anexemplary embodiment.

FIG. 5 is a block diagram of a system for managing a digital twin wherean artificial intelligence agent can be executed to infer informationfor an entity of a graph, according to an exemplary embodiment.

FIG. 6 is a flow diagram of a process for executing an artificialintelligence agent to infer and/or predict information, according to anexemplary embodiment.

FIG. 7 is a flow diagram an agent of a digital twin executing a triggerrule and an action rule, according to an exemplary embodiment.

FIG. 8 is a block diagram of a system where a clean air optimization(CAO) AI service and an energy prediction model (EPM) AI service operateto make inferences and predictions based on data of a knowledge graph,according to an exemplary embodiment.

FIG. 9 is a block diagram of a CAO AI agent and an EPM AI agentoperating against the knowledge graph of FIG. 26 to generate inferencesand predictions, according to an exemplary embodiment.

FIG. 10 is a block diagram of the edge platform of FIG. 1 performingevent enrichment at the edge before the events are communicated to thecloud, according to an exemplary embodiment.

FIG. 11 is a block diagram a building graph divided and distributedacross a cloud system and an edge system, according to an exemplaryembodiment.

FIG. 12 is a block diagram of the twin manager of FIG. 1 and an edgedevice storing the building graph of FIG. 11 divided and distributedacross the twin manager and the edge device, according to an exemplaryembodiment.

FIG. 13 is a block diagram of the distributed building graph generatedacross the twin manager and a building controller during an onboardingprocess, according to an exemplary embodiment.

FIG. 14 is a flow diagram of a process of querying a building graphdivided into multiple building graphs distributed across cloud and edgesystems, according to an exemplary embodiment.

FIG. 15 is a flow diagram of a process of querying a building graphdivided into multiple building graphs distributed across cloud and edgesystems by an agent, and ingesting information back into the buildinggraph by the agent, according to an exemplary embodiment.

FIG. 16 is a flow diagram of a process of querying a building graphdivided into multiple graphs distributed across a cloud system and anedge platform and using information queried from the building graph toperform one or more operations, according to an exemplary embodiment.

FIG. 17 is a flow diagram of a process where the distributed buildinggraph is generated across the twin manager and a building controllerduring onboarding, according to an exemplary embodiment.

DETAILED DESCRIPTION Overview

Referring generally to the FIGURES, systems and methods for distributinga digital twin of a building across cloud and edge devices are shown,according to various exemplary embodiments. A digital twin can be avirtual representation of a building and/or an entity of the building(e.g., space, piece of equipment, occupant, etc.). Furthermore, thedigital twin can represent a service performed in a building, e.g.,facility management, clean air optimization, energy prediction,equipment maintenance, etc.

In some embodiments, the digital twin can include an information datastore and a connector. The information data store can store theinformation describing the entity that the digital twin operates for(e.g., attributes of the entity, measurements associated with theentity, control points or commands of the entity, etc.). In someembodiments, the data store can be a graph including various nodes andedges. The connector can be a software component that provides telemetryfrom the entity (e.g., physical device) to the information store.Furthermore, the digital twin can include an artificial intelligence(AI), e.g., an AI agent. The AI can be one or more rules based engines,machine learning algorithms, and/or models that operate based oninformation of the information data store and output information. The AIagent can run against the digital twin. In some embodiments, the AIagent can run against a common data model, e.g., a BRICK model, and canbe easily implemented in various different buildings, e.g., againstvarious different building models of the system format.

In some embodiments, the AI agent for the digital twin can call an AIservice to determine inferences and/or predict future data values. Insome embodiments, the predictions are potential future states. In someembodiments, the predictions predict a timeseries of a data point intothe future. The predictions could be predicted indoor temperature for anhour, inferred future air quality from 15 minute air quality readings,etc. In some embodiments, the digital twin can store predicted and/orinferred information in a graph data store as a node in the graph datastore related to an entity that the digital twin represents or otherwiseoperates for. In some embodiments, the digital twin, or other digitaltwins, can operate against the predicted and/or inferred data, e.g.,operate to construct and implement control algorithms for operatingequipment of a building based on predicted future data points of thebuilding.

Some systems may implement a digital twin on a cloud platform only.However, such a system may not be able to handle a hybrid implementationof a digital twin where the digital twin is stored across a one or morecloud and/or edge systems. In some embodiments, the building systemdescribed herein can distribute the digital twin across one or morecloud and/or edge systems. In some embodiments, operational capabilitiesof a digital twin can be distributed and/or implemented by the buildingsystem across the one or more cloud and/or edge systems.

In some embodiments, a building graph (which may be part of a digitaltwin or make up the digital twin) can be distributed across the one ormore cloud and/or edge systems. The building graph can be divided intoone or more interrelated building graphs that are distributed. In thisregard, information pertaining to a particular edge system can be storedin a building graph specific to the edge system and interrelated toother building graphs stored in other cloud and/or edge systems. In thisregard, algorithms, analytics, computing elements, etc. of theparticular edge system can run against the local building graph.

In some embodiments, each building graph distributed across the one ormore edge and/or cloud systems can be connected to each other. Forexample, a first building graph may store one or more nodes or edgesthat connect the first building graph to a second building graph storedby a second system. In this regard, a first system can traverse thenodes or edges of the first building graph that the first system storesto identify a second building graph stored by a second system, thesecond building graph storing information needed to fill a query of thefirst system. The first system can send the query to the identifiedsecond system and receive a result of the query filled by the secondsystem based on the second building graph.

In some embodiments, the divided and distributed building graph can helpseparate operating concerns through localizing operations. In someembodiments, the building system can distribute responsibilities tovarious edge and/or cloud systems. Because each edge system handles itsown responsibilities with its own graph, the edge system may not need todelay data management or control for passing data or states between theedge system and a central cloud platform. In some embodiments, theportion of the building graph stored by each edge and/or cloud systemcan include its own format extensions and/or features. For example, anedge system that manages video surveillance systems may store its graphin a formatted extended with specific data types, attributes,relationship types etc. specific to video surveillance systems while asecond HVAC system may store its graph in the same format but withextensions for specific data types, attributes, relationship types, etc.specific to HVAC systems.

In some embodiments, distributing and/or dividing the building graphacross multiple cloud and/or edge systems can resolve security issues.In some embodiments, data may be more secure if the data stays within abuilding and does not need to be transferred via one or more externalnetworks from the building to a cloud system. Because the edge systemscan store their own building graphs and perform operations based on theedge systems, the data of the building may not need to be transferredoutside the building and thus is less likely to be obtained by otherentities.

The divided building graph can, in some embodiments, provide flexibilityin where digital twin computations are performed. For example, becauseeach cloud and/or edge system can include the building graph that eachcloud and/or edge system needs, each cloud and/or edge system canlocally run computational functions against the building graph that thesystem stores. In some embodiments, functions such as agents can runlocally within each system. Examples of agents and agent relatedprocessing can be found in U.S. patent application Ser. No. 17/354,436filed Jun. 22, 2021, U.S. patent application Ser. No. 17/354,338 filedJun. 22, 2021, U.S. patent application Ser. No. 17/148,851 filed Jan.14, 2021, U.S. patent application Ser. No. 15/723,624 filed Oct. 3,2017, U.S. patent application Ser. No. 16/008,885 filed Jun. 14, 2018,U.S. patent application Ser. No. 16/143,243 filed Sep. 26, 2018, U.S.patent application Ser. No. 16/533,499 filed Aug. 6, 2019, and U.S.patent application Ser. No. 16/142,859 filed Aug. 26, 2018, the entiretyof which is incorporated by reference herein.

Referring now to FIG. 1 , a building data platform 100 including an edgeplatform 102, a cloud platform 106, and a twin manager 108 are shown,according to an exemplary embodiment. The edge platform 102, the cloudplatform 106, and the twin manager 108 can each be separate servicesdeployed on the same or different computing systems. In someembodiments, the cloud platform 106 and the twin manager 108 areimplemented in off premises computing systems, e.g., outside a building.The edge platform 102 can be implemented on-premises, e.g., within thebuilding. However, any combination of on-premises and off-premisescomponents of the building data platform 100 can be implemented.

The building data platform 100 includes applications 110. Theapplications 110 can be various applications that operate to manage thebuilding subsystems 122. The applications 110 can be remote oron-premises applications (or a hybrid of both) that run on variouscomputing systems. The applications 110 can include an alarm application168 configured to manage alarms for the building subsystems 122. Theapplications 110 include an assurance application 170 that implementsassurance services for the building subsystems 122. In some embodiments,the applications 110 include an energy application 172 configured tomanage the energy usage of the building subsystems 122. The applications110 include a security application 174 configured to manage securitysystems of the building.

In some embodiments, the applications 110 and/or the cloud platform 106interacts with a user device 176. In some embodiments, a component or anentire application of the applications 110 runs on the user device 176.The user device 176 may be a laptop computer, a desktop computer, asmartphone, a tablet, and/or any other device with an input interface(e.g., touch screen, mouse, keyboard, etc.) and an output interface(e.g., a speaker, a display, etc.).

The applications 110, the twin manager 108, the cloud platform 106, andthe edge platform 102 can be implemented on one or more computingsystems, e.g., on processors and/or memory devices. For example, theedge platform 102 includes processor(s) 118 and memories 120, the cloudplatform 106 includes processor(s) 124 and memories 126, theapplications 110 include processor(s) 164 and memories 166, and the twinmanager 108 includes processor(s) 148 and memories 150.

The processors can be a general purpose or specific purpose processors,an application specific integrated circuit (ASIC), one or more fieldprogrammable gate arrays (FPGAs), a group of processing components, orother suitable processing components. The processors may be configuredto execute computer code and/or instructions stored in the memories orreceived from other computer readable media (e.g., CDROM, networkstorage, a remote server, etc.).

The memories can include one or more devices (e.g., memory units, memorydevices, storage devices, etc.) for storing data and/or computer codefor completing and/or facilitating the various processes described inthe present disclosure. The memories can include random access memory(RAM), read-only memory (ROM), hard drive storage, temporary storage,non-volatile memory, flash memory, optical memory, or any other suitablememory for storing software objects and/or computer instructions. Thememories can include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described in thepresent disclosure. The memories can be communicably connected to theprocessors and can include computer code for executing (e.g., by theprocessors) one or more processes described herein.

The edge platform 102 can be configured to provide connection to thebuilding subsystems 122. The edge platform 102 can receive messages fromthe building subsystems 122 and/or deliver messages to the buildingsubsystems 122. The edge platform 102 includes one or multiple gateways,e.g., the gateways 112-116. The gateways 112-116 can act as a gatewaybetween the cloud platform 106 and the building subsystems 122. Thegateways 112-116 can be the gateways described in U.S. ProvisionalPatent Application No. 62/951,897 filed Dec. 20, 2019, the entirety ofwhich is incorporated by reference herein. In some embodiments, theapplications 110 can be deployed on the edge platform 102. In thisregard, lower latency in management of the building subsystems 122 canbe realized.

The edge platform 102 can be connected to the cloud platform 106 via anetwork 104. The network 104 can communicatively couple the devices andsystems of building data platform 100. In some embodiments, the network104 is at least one of and/or a combination of a Wi-Fi network, a wiredEthernet network, a ZigBee network, a Bluetooth network, and/or anyother wireless network. The network 104 may be a local area network or awide area network (e.g., the Internet, a building WAN, etc.) and may usea variety of communications protocols (e.g., BACnet, IP, LON, etc.). Thenetwork 104 may include routers, modems, servers, cell towers,satellites, and/or network switches. The network 104 may be acombination of wired and wireless networks.

The cloud platform 106 can be configured to facilitate communication androuting of messages between the applications 110, the twin manager 108,the edge platform 102, and/or any other system. The cloud platform 106can include a platform manager 128, a messaging manager 140, a commandprocessor 136, and an enrichment manager 138. In some embodiments, thecloud platform 106 can facilitate messaging between the building dataplatform 100 via the network 104.

The messaging manager 140 can be configured to operate as a transportservice that controls communication with the building subsystems 122and/or any other system, e.g., managing commands to devices (C2D),commands to connectors (C2C) for external systems, commands from thedevice to the cloud (D2C), and/or notifications. The messaging manager140 can receive different types of data from the applications 110, thetwin manager 108, and/or the edge platform 102. The messaging manager140 can receive change on value data 142, e.g., data that indicates thata value of a point has changed. The messaging manager 140 can receivetimeseries data 144, e.g., a time correlated series of data entries eachassociated with a particular time stamp. Furthermore, the messagingmanager 140 can receive command data 146. All of the messages handled bythe cloud platform 106 can be handled as an event, e.g., the data142-146 can each be packaged as an event with a data value occurring ata particular time (e.g., a temperature measurement made at a particulartime).

The cloud platform 106 includes a command processor 136. The commandprocessor 136 can be configured to receive commands to perform an actionfrom the applications 110, the building subsystems 122, the user device176, etc. The command processor 136 can manage the commands, determinewhether the commanding system is authorized to perform the particularcommands, and communicate the commands to the commanded system, e.g.,the building subsystems 122 and/or the applications 110. The commandscould be a command to change an operational setting that controlenvironmental conditions of a building, a command to run analytics, etc.

The cloud platform 106 includes an enrichment manager 138. Theenrichment manager 138 can be configured to enrich the events receivedby the messaging manager 140. The enrichment manager 138 can beconfigured to add contextual information to the events. The enrichmentmanager 138 can communicate with the twin manager 108 to retrieve thecontextual information. In some embodiments, the contextual informationis an indication of information related to the event. For example, ifthe event is a timeseries temperature measurement of a thermostat,contextual information such as the location of the thermostat (e.g.,what room), the equipment controlled by the thermostat (e.g., what VAV),etc. can be added to the event. In this regard, when a consumingapplication, e.g., one of the applications 110 receives the event, theconsuming application can operate based on the data of the event, thetemperature measurement, and also the contextual information of theevent.

The enrichment manager 138 can solve a problem that when a deviceproduces a significant amount of information, the information maycontain simple data without context. An example might include the datagenerated when a user scans a badge at a badge scanner of the buildingsubsystems 122. This physical event can generate an output eventincluding such information as “DeviceBadgeScannerID,” “BadgeID,” and/or“Date/Time.” However, if a system sends this data to a consumingapplication, e.g., Consumer A and a Consumer B, each customer may needto call the building data platform knowledge service to queryinformation with queries such as, “What space, build, floor is thatbadge scanner in?” or “What user is associated with that badge?”

By performing enrichment on the data feed, a system can be able toperform inferences on the data. A result of the enrichment may betransformation of the message “DeviceBadgeScannerId, BadgeId,Date/Time,” to “Region, Building, Floor, Asset, DeviceId, BadgeId,UserName, EmployeeId, Date/Time Scanned.” This can be a significantoptimization, as a system can reduce the number of calls by 1/n, where nis the number of consumers of this data feed.

By using this enrichment, a system can also have the ability to filterout undesired events. If there are 100 building in a campus that receive100,000 events per building each hour, but only 1 building is actuallycommissioned, only 1/10 of the events are enriched. By looking at whatevents are enriched and what events are not enriched, a system can dotraffic shaping of forwarding of these events to reduce the cost offorwarding events that no consuming application wants or reads.

An example of an event received by the enrichment manager 138 may be:

{ “id”: “someguid”, “eventType”: “Device_Heartbeat”, “eventTime”:“2018-01-27T00:00:00+00:00” “eventValue”: 1, “deviceID”: “someguid” }

An example of an enriched event generated by the enrichment manager 138may be:

{ “id”: “someguid”, “eventType”: “Device_Heartbeat”, “eventTime”:“2018-01-27T00:00:00+00:00” “eventValue”: 1, “deviceID”: “someguid”,“buildingName”: “Building-48”, “buildingID”: “SomeGuid”, “panelID”:“SomeGuid”, “panelName”: “Building-48-Panel-13”, “cityID”: 371,“cityName”: “Milwaukee”, “stateID”: 48, “stateName”: “Wisconsin (WI)”,“countryID”: 1, “countryName”: “United States” }

By receiving enriched events, an application of the applications 110 canbe able to populate and/or filter what events are associated with whatareas. Furthermore, user interface generating applications can generateuser interfaces that include the contextual information based on theenriched events.

The cloud platform 106 includes a platform manager 128. The platformmanager 128 can be configured to manage the users and/or subscriptionsof the cloud platform 106. For example, what subscribing building, user,and/or tenant utilizes the cloud platform 106. The platform manager 128includes a provisioning service 130 configured to provision the cloudplatform 106, the edge platform 102, and the twin manager 108. Theplatform manager 128 includes a subscription service 132 configured tomanage a subscription of the building, user, and/or tenant while theentitlement service 134 can track entitlements of the buildings, users,and/or tenants.

The twin manager 108 can be configured to manage and maintain a digitaltwin. The digital twin can be a digital representation of the physicalenvironment, e.g., a building. The twin manager 108 can include a changefeed generator 152, a schema and ontology 154, a graph projectionmanager 156, a policy manager 158, an entity, relationship, and eventdatabase 160, and a graph projection database 162.

The graph projection manager 156 can be configured to construct graphprojections and store the graph projections in the graph projectiondatabase 162. Examples of graph projections are shown in FIGS. 11-13 .Entities, relationships, and events can be stored in the database 160.The graph projection manager 156 can retrieve entities, relationships,and/or events from the database 160 and construct a graph projectionbased on the retrieved entities, relationships and/or events. In someembodiments, the database 160 includes an entity-relationship collectionfor multiple subscriptions.

In some embodiment, the graph projection manager 156 generates a graphprojection for a particular user, application, subscription, and/orsystem. In this regard, the graph projection can be generated based onpolicies for the particular user, application, and/or system in additionto an ontology specific for that user, application, and/or system. Inthis regard, an entity could request a graph projection and the graphprojection manager 156 can be configured to generate the graphprojection for the entity based on policies and an ontology specific tothe entity. The policies can indicate what entities, relationships,and/or events the entity has access to. The ontology can indicate whattypes of relationships between entities the requesting entity expects tosee, e.g., floors within a building, devices within a floor, etc.Another requesting entity may have an ontology to see devices within abuilding and applications for the devices within the graph.

The graph projections generated by the graph projection manager 156 andstored in the graph projection database 162 can be a knowledge graph andis an integration point. For example, the graph projections canrepresent floor plans and systems associated with each floor.Furthermore, the graph projections can include events, e.g., telemetrydata of the building subsystems 122. The graph projections can showapplication services as nodes and API calls between the services asedges in the graph. The graph projections can illustrate thecapabilities of spaces, users, and/or devices. The graph projections caninclude indications of the building subsystems 122, e.g., thermostats,cameras, VAVs, etc. The graph projection database 162 can store graphprojections that keep up a current state of a building.

The graph projections of the graph projection database 162 can bedigital twins of a building. Digital twins can be digital replicas ofphysical entities that enable an in-depth analysis of data of thephysical entities and provide the potential to monitor systems tomitigate risks, manage issues, and utilize simulations to test futuresolutions. Digital twins can play an important role in helpingtechnicians find the root cause of issues and solve problems faster, insupporting safety and security protocols, and in supporting buildingmanagers in more efficient use of energy and other facilities resources.Digital twins can be used to enable and unify security systems, employeeexperience, facilities management, sustainability, etc.

In some embodiments the enrichment manager 138 can use a graphprojection of the graph projection database 162 to enrich events. Insome embodiments, the enrichment manager 138 can identify nodes andrelationships that are associated with, and are pertinent to, the devicethat generated the event. For example, the enrichment manager 138 couldidentify a thermostat generating a temperature measurement event withinthe graph. The enrichment manager 138 can identify relationships betweenthe thermostat and spaces, e.g., a zone that the thermostat is locatedin. The enrichment manager 138 can add an indication of the zone to theevent.

Furthermore, the command processor 136 can be configured to utilize thegraph projections to command the building subsystems 122. The commandprocessor 136 can identify a policy for a commanding entity within thegraph projection to determine whether the commanding entity has theability to make the command. For example, the command processor 136,before allowing a user to make a command, determine, based on the graphprojection database 162, to determine that the user has a policy to beable to make the command.

In some embodiments, the policies can be conditional based policies. Forexample, the building data platform 100 can apply one or moreconditional rules to determine whether a particular system has theability to perform an action. In some embodiments, the rules analyze abehavioral based biometric. For example, a behavioral based biometriccan indicate normal behavior and/or normal behavior rules for a system.In some embodiments, when the building data platform 100 determines,based on the one or more conditional rules, that an action requested bya system does not match a normal behavior, the building data platform100 can deny the system the ability to perform the action and/or requestapproval from a higher level system.

For example, a behavior rule could indicate that a user has access tolog into a system with a particular IP address between 8 A.M. through 5P.M. However, if the user logs in to the system at 7 P.M., the buildingdata platform 100 may contact an administrator to determine whether togive the user permission to log in.

The change feed generator 152 can be configured to generate a feed ofevents that indicate changes to the digital twin, e.g., to the graph.The change feed generator 152 can track changes to the entities,relationships, and/or events of the graph. For example, the change feedgenerator 152 can detect an addition, deletion, and/or modification of anode or edge of the graph, e.g., changing the entities, relationships,and/or events within the database 160. In response to detecting a changeto the graph, the change feed generator 152 can generate an eventsummarizing the change. The event can indicate what nodes and/or edgeshave changed and how the nodes and edges have changed. The events can beposted to a topic by the change feed generator 152.

The change feed generator 152 can implement a change feed of a knowledgegraph. The building data platform 100 can implement a subscription tochanges in the knowledge graph. When the change feed generator 152 postsevents in the change feed, subscribing systems or applications canreceive the change feed event. By generating a record of all changesthat have happened, a system can stage data in different ways, and thenreplay the data back in whatever order the system wishes. This caninclude running the changes sequentially one by one and/or by jumpingfrom one major change to the next. For example, to generate a graph at aparticular time, all change feed events up to the particular time can beused to construct the graph.

The change feed can track the changes in each node in the graph and therelationships related to them, in some embodiments. If a user wants tosubscribe to these changes and the user has proper access, the user cansimply submit a web API call to have sequential notifications of eachchange that happens in the graph. A user and/or system can replay thechanges one by one to reinstitute the graph at any given time slice.Even though the messages are “thin” and only include notification ofchange and the reference “id/seq id,” the change feed can keep a copy ofevery state of each node and/or relationship so that a user and/orsystem can retrieve those past states at any time for each node.Furthermore, a consumer of the change feed could also create dynamic“views” allowing different “snapshots” in time of what the graph lookslike from a particular context. While the twin manager 108 may containthe history and the current state of the graph based upon schemaevaluation, a consumer can retain a copy of that data, and therebycreate dynamic views using the change feed.

The schema and ontology 154 can define the message schema and graphontology of the twin manager 108. The message schema can define whatformat messages received by the messaging manager 140 should have, e.g.,what parameters, what formats, etc. The ontology can define graphprojections, e.g., the ontology that a user wishes to view. For example,various systems, applications, and/or users can be associated with agraph ontology. Accordingly, when the graph projection manager 156generates an graph projection for a user, system, or subscription, thegraph projection manager 156 can generate a graph projection accordingto the ontology specific to the user. For example, the ontology candefine what types of entities are related in what order in a graph, forexample, for the ontology for a subscription of “Customer A,” the graphprojection manager 156 can create relationships for a graph projectionbased on the rule:

-   -   Region        Building        Floor        Space        Asset

For the ontology of a subscription of “Customer B,” the graph projectionmanager 156 can create relationships based on the rule:

-   -   Building        Floor        Asset

The policy manager 158 can be configured to respond to requests fromother applications and/or systems for policies. The policy manager 158can consult a graph projection to determine what permissions differentapplications, users, and/or devices have. The graph projection canindicate various permissions that different types of entities have andthe policy manager 158 can search the graph projection to identify thepermissions of a particular entity. The policy manager 158 canfacilitate fine grain access control with user permissions. The policymanager 158 can apply permissions across a graph, e.g., if “user canview all data associated with floor 1” then they see all subsystem datafor that floor, e.g., surveillance cameras, HVAC devices, fire detectionand response devices, etc.

The twin manager 108 includes a query manager 165 and a twin functionmanager 167. The query manger 164 can be configured to handle queriesreceived from a requesting system, e.g., the user device 176, theapplications 110, and/or any other system. The query manager 165 canreceive queries that include query parameters and context. The querymanager 165 can query the graph projection database 162 with the queryparameters to retrieve a result. The query manager 165 can then cause anevent processor, e.g., a twin function, to operate based on the resultand the context. In some embodiments, the query manager 165 can selectthe twin function based on the context and/or perform operates based onthe context.

The twin function manager 167 can be configured to manage the executionof twin functions. The twin function manager 167 can receive anindication of a context query that identifies a particular data elementand/or pattern in the graph projection database 162. Responsive to theparticular data element and/or pattern occurring in the graph projectiondatabase 162 (e.g., based on a new data event added to the graphprojection database 162 and/or change to nodes or edges of the graphprojection database 162, the twin function manager 167 can cause aparticular twin function to execute. The twin function can execute basedon an event, context, and/or rules. The event can be data that the twinfunction executes against. The context can be information that providesa contextual description of the data, e.g., what device the event isassociated with, what control point should be updated based on theevent, etc.

Referring now to FIG. 2 , a graph projection 200 of the twin manager 108including application programming interface (API) data, capability data,policy data, and services is shown, according to an exemplaryembodiment. The graph projection 200 includes nodes 202-240 and edges250-272. The nodes 202-240 and the edges 250-272 are defined accordingto the key 201. The nodes 202-240 represent different types of entities,devices, locations, points, persons, policies, and software services(e.g., API services). The edges 250-272 represent relationships betweenthe nodes 202-240, e.g., dependent calls, API calls, inferredrelationships, and schema relationships (e.g., BRICK relationships).

The graph projection 200 includes a device hub 202 which may represent asoftware service that facilitates the communication of data and commandsbetween the cloud platform 106 and a device of the building subsystems122, e.g., door actuator 214. The device hub 202 is related to aconnector 204, an external system 206, and a digital asset “DoorActuator” 208 by edge 250, edge 252, and edge 254.

The cloud platform 106 can be configured to identify the device hub 202,the connector 204, the external system 206 related to the door actuator214 by searching the graph projection 200 and identifying the edges250-254 and edge 258. The graph projection 200 includes a digitalrepresentation of the “Door Actuator,” node 208. The digital asset “DoorActuator” 208 includes a “DeviceNameSpace” represented by node 207 andrelated to the digital asset “Door Actuator” 208 by the “Property ofObject” edge 256.

The “Door Actuator” 214 has points and timeseries. The “Door Actuator”214 is related to “Point A” 216 by a “has_a” edge 260. The “DoorActuator” 214 is related to “Point B” 218 by a “has_a” edge 258.Furthermore, timeseries associated with the points A and B arerepresented by nodes “TS” 220 and “TS” 222. The timeseries are relatedto the points A and B by “has_a” edge 264 and “has_a” edge 262. Thetimeseries “TS” 220 has particular samples, sample 210 and 212 eachrelated to “TS” 220 with edges 268 and 266 respectively. Each sampleincludes a time and a value. Each sample may be an event received fromthe door actuator that the cloud platform 106 ingests into the entity,relationship, and event database 160, e.g., ingests into the graphprojection 200.

The graph projection 200 includes a building 234 representing a physicalbuilding. The building includes a floor represented by floor 232 relatedto the building 234 by the “has a” edge from the building 234 to thefloor 232. The floor has a space indicated by the edge “has_a” 270between the floor 232 and the space 230. The space has particularcapabilities, e.g., is a room that can be booked for a meeting,conference, private study time, etc. Furthermore, the booking can becanceled. The capabilities for the floor 232 are represented bycapabilities 228 related to space 230 by edge 280. The capabilities 228are related to two different commands, command “book room” 224 andcommand “cancel booking” 226 related to capabilities 228 by edge 284 andedge 282 respectively.

If the cloud platform 106 receives a command to book the spacerepresented by the node, space 230, the cloud platform 106 can searchthe graph projection 200 for the capabilities for the 228 related to thespace 230 to determine whether the cloud platform 106 can book the room.

In some embodiments, the cloud platform 106 could receive a request tobook a room in a particular building, e.g., the building 234. The cloudplatform 106 could search the graph projection 200 to identify spacesthat have the capabilities to be booked, e.g., identify the space 230based on the capabilities 228 related to the space 230. The cloudplatform 106 can reply to the request with an indication of the spaceand allow the requesting entity to book the space 230.

The graph projection 200 includes a policy 236 for the floor 232. Thepolicy 236 is related set for the floor 232 based on a “To Floor” edge274 between the policy 236 and the floor 232. The policy 236 is relatedto different roles for the floor 232, read events 238 via edge 276 andsend command 240 via edge 278. The policy 236 is set for the entity 203based on has edge 251 between the entity 203 and the policy 236.

The twin manager 108 can identify policies for particular entities,e.g., users, software applications, systems, devices, etc. based on thepolicy 236. For example, if the cloud platform 106 receives a command tobook the space 230. The cloud platform 106 can communicate with the twinmanager 108 to verify that the entity requesting to book the space 230has a policy to book the space. The twin manager 108 can identify theentity requesting to book the space as the entity 203 by searching thegraph projection 200. Furthermore, the twin manager 108 can furtheridentify the edge has 251 between the entity 203 and the policy 236 andthe edge 1178 between the policy 236 and the command 240.

Furthermore, the twin manager 108 can identify that the entity 203 hasthe ability to command the space 230 based on the edge 1174 between thepolicy 236 and the edge 270 between the floor 232 and the space 230. Inresponse to identifying the entity 203 has the ability to book the space230, the twin manager 108 can provide an indication to the cloudplatform 106.

Furthermore, if the entity makes a request to read events for the space230, e.g., the sample 210 and the sample 212, the twin manager 108 canidentify the edge has 251 between the entity 203 and the policy 236, theedge 1178 between the policy 236 and the read events 238, the edge 1174between the policy 236 and the floor 232, the “has_a” edge 270 betweenthe floor 232 and the space 230, the edge 268 between the space 230 andthe door actuator 214, the edge 260 between the door actuator 214 andthe point A 216, the “has_a” edge 264 between the point A 216 and the TS220, and the edges 268 and 266 between the TS 220 and the samples 210and 212 respectively.

Referring now to FIG. 3 , a graph projection 300 of the twin manager 108including application programming interface (API) data, capability data,policy data, and services is shown, according to an exemplaryembodiment. The graph projection 300 includes the nodes and edgesdescribed in the graph projection 200 of FIG. 2 . The graph projection300 includes a connection broker 310 related to capabilities 228 by edge398 a. The connection broker 310 can be a node representing a softwareapplication configured to facilitate a connection with another softwareapplication. In some embodiments, the cloud platform 106 can identifythe system that implements the capabilities 228 by identifying the edge398 a between the capabilities 228 and the connection broker 310.

The connection broker 310 is related to an agent that optimizes a space356 via edge 398 b. The agent represented by the node 356 can book andcancel bookings for the space represented by the node 230 based on theedge 398 b between the connection broker 310 and the node 356 and theedge 398 a between the capabilities 228 and the connection broker 310.

The connection broker 310 is related to a cluster 308 by edge 398 c.Cluster 308 is related to connector B 302 via edge 398 e and connector A306 via edge 398 d. The connector A 306 is related to an externalsubscription service 304. A connection broker 310 is related to cluster308 via an edge 311 representing a rest call that the connection brokerrepresented by node 310 can make to the cluster represented by cluster308.

The connection broker 310 is related to a virtual meeting platform 312by an edge 354. The node 312 represents an external system thatrepresents a virtual meeting platform. The connection broker representedby node 310 can represent a software component that facilitates aconnection between the cloud platform 106 and the virtual meetingplatform represented by node 312. When the cloud platform 106 needs tocommunicate with the virtual meeting platform represented by the node312, the cloud platform 106 can identify the edge 354 between theconnection broker 310 and the virtual meeting platform 312 and selectthe connection broker represented by the node 310 to facilitatecommunication with the virtual meeting platform represented by the node312.

A capabilities node 318 can be connected to the connection broker 310via edge 360. The capabilities 318 can be capabilities of the virtualmeeting platform represented by the node 312 and can be related to thenode 312 through the edge 360 to the connection broker 310 and the edge354 between the connection broker 310 and the node 312. The capabilities318 can define capabilities of the virtual meeting platform representedby the node 312. The node 320 is related to capabilities 318 via edge362. The capabilities may be an invite bob command represented by node316 and an email bob command represented by node 314. The capabilities318 can be linked to a node 320 representing a user, Bob. The cloudplatform 106 can facilitate email commands to send emails to the userBob via the email service represented by the node 304. The node 304 isrelated to the connect a node 306 via edge 398 f Furthermore, the cloudplatform 106 can facilitate sending an invite for a virtual meeting viathe virtual meeting platform represented by the node 312 linked to thenode 318 via the edge 358.

The node 320 for the user Bob can be associated with the policy 236 viathe “has” edge 364. Furthermore, the node 320 can have a “check policy”edge 366 with a portal node 324. The device API node 328 has a checkpolicy edge 370 to the policy node 236. The portal node 324 has an edge368 to the policy node 236. The portal node 324 has an edge 323 to anode 326 representing a user input manager (UIM). The portal node 324 isrelated to the UIM node 326 via an edge 323. The UIM node 326 has anedge 323 to a device API node 328. The UIM node 326 is related to thedoor actuator node 214 via edge 372. The door actuator node 214 has anedge 374 to the device API node 328. The door actuator 214 has an edge335 to the connector virtual object 334. The device hub 332 is relatedto the connector virtual object via edge 380. The device API node 328can be an API for the door actuator 214. The connector virtual object334 is related to the device API node 328 via the edge 331.

The device API node 328 is related to a transport connection broker 330via an edge 329. The transport connection broker 330 is related to adevice hub 332 via an edge 378. The device hub represented by node 332can be a software component that hands the communication of data andcommands for the door actuator 214. The cloud platform 106 can identifywhere to store data within the graph projection 300 received from thedoor actuator by identifying the nodes and edges between the points 216and 218 and the device hub node 332. Similarly, the cluster 308 canidentify commands for the door actuator that can be facilitated by thedevice hub represented by the node 332, e.g., by identifying edgesbetween the device hub node 332 and an open door node 352 and an lockdoor node 350. The door actuator 114 has an edge “has mapped an asset”280 between the node 214 and a capabilities node 348. The capabilitiesnode 348 and the nodes 352 and 350 are linked by edges 396 and 394.

The device hub 332 is linked to a cluster 336 via an edge 384. Thecluster 336 is linked to connector A 340 and connector B 338 by edges386 and the edge 389. The connector A 340 and the connector B 338 islinked to an external system 344 via edges 388 and 390. The externalsystem 344 is linked to a door actuator 342 via an edge 392.

Referring now to FIG. 4 , a graph projection 400 of the twin manager 108including equipment and capability data for the equipment is shown,according to an exemplary embodiment. The graph projection 400 includesnodes 402-456 and edges 360-498 f. The cloud platform 106 can search thegraph projection 400 to identify capabilities of different pieces ofequipment.

A building node 404 represents a particular building that includes twofloors. A floor 1 node 402 is linked to the building node 404 via edge460 while a floor 2 node 406 is linked to the building node 404 via edge462. The floor 2 includes a particular room 2023 represented by edge 464between floor 2 node 406 and room 2023 node 408. Various pieces ofequipment are included within the room 2023. A light represented bylight node 416, a bedside lamp node 414, a bedside lamp node 412, and ahallway light node 410 are related to room 2023 node 408 via edge 466,edge 472, edge 470, and edge 468.

The light represented by light node 416 is related to a light connector426 via edge 484. The light connector 426 is related to multiplecommands for the light represented by the light node 416 via edges 484,486, and 488. The commands may be a brightness setpoint 424, an oncommand 425, and a hue setpoint 428. The cloud platform 106 can receivea request to identify commands for the light represented by the light416 and can identify the nodes 424-428 and provide an indication of thecommands represented by the node 424-428 to the requesting entity. Therequesting entity can then send commands for the commands represented bythe nodes 424-428.

The bedside lamp node 414 is linked to a bedside lamp connector 481 viaan edge 413. The connector 481 is related to commands for the bedsidelamp represented by the bedside lamp node 414 via edges 492, 496, and494. The command nodes are a brightness setpoint node 432, an on commandnode 434, and a color command 436. The hallway light 410 is related to ahallway light connector 446 via an edge 498 d. The hallway lightconnector 446 is linked to multiple commands for the hallway light node410 via edges 498 g, 498 f, and 498 e. The commands are represented byan on command node 452, a hue setpoint node 450, and a light bulbactivity node 448.

The graph projection 400 includes a name space node 422 related to aserver A node 418 and a server B node 420 via edges 474 and 476. Thename space node 422 is related to the bedside lamp connector 481, thebedside lamp connector 444, and the hallway light connector 446 viaedges 482, 480, and 478. The bedside lamp connector 444 is related tocommands, e.g., the color command node 440, the hue setpoint command438, a brightness setpoint command 456, and an on command 454 via edges498 c, 498 b, 498 a, and 498.

Referring now to FIG. 5 , a system 500 for managing a digital twin wherean artificial intelligence agent can be executed to infer and/or predictinformation for an entity of a graph is shown, according to an exemplaryembodiment. The system 500 can be components of the building dataplatform 100, e.g., components run on the processors and memories of theedge platform 102, the cloud platform 106, the twin manager 108, and/orthe applications 110. The system 500 can, in some implementations,implement a digital twin with artificial intelligence.

A digital twin (or a shadow) may be a computing entity that describes aphysical thing (e.g., a building, spaces of a building, devices of abuilding, people of the building, equipment of the building, etc.)through modeling the physical thing through a set of attributes thatdefine the physical thing. A digital twin can refer to a digital replicaof physical assets (a physical device twin) and can be extended to storeprocesses, people, places, systems that can be used for variouspurposes. The digital twin can include both the ingestion of informationand actions learned and executed through artificial intelligence agents.

In FIG. 5 , the digital twin can be a graph 529 managed by the twinmanager 108 and/or artificial intelligence agents 570. In someembodiments, the digital twin is the combination of the graph 529 withthe artificial intelligence agents 570. In some embodiments, the digitaltwin enables the creation of a chronological time-series database oftelemetry events for analytical purposes. In some embodiments, the graph529 uses the BRICK schema.

The twin manager 108 stores the graph 529 which may be a graph datastructure including various nodes and edges interrelating the nodes. Thegraph 529 may be the same as, or similar to, the graph projectionsdescribed herein with reference to FIGS. 1-4 . The graph 529 includesnodes 510-526 and edges 528-546. The graph 529 includes a building node526 representing a building that has a floor indicated by the “has” edge546 to the floor node 522. The floor node 522 is relate to a zone node510 via a “has” edge 544 indicating that the floor represented by thenode 522 has a zone represented by the zone 510.

The floor node 522 is related to the zone node 518 by the “has” edge 540indicating that the floor represented by the floor node 522 has anotherzone represented by the zone node 518. The floor node 522 is related toanother zone node 524 via a “has” edge 542 representing that the floorrepresented by the floor node 522 has a third zone represented by thezone node 524.

The graph 529 includes an AHU node 514 representing an AHU of thebuilding represented by the building node 526. The AHU node 514 isrelated by a “supplies” edge 530 to the VAV node 512 to represent thatthe AHU represented by the AHU node 514 supplies air to the VAVrepresented by the VAV node 512. The AHU node 514 is related by a“supplies” edge 536 to the VAV node 520 to represent that the AHUrepresented by the AHU node 514 supplies air to the VAV represented bythe VAV node 520. The AHU node 514 is related by a “supplies” edge 532to the VAV node 516 to represent that the AHU represented by the AHUnode 514 supplies air to the VAV represented by the VAV node 516.

The VAV node 516 is related to the zone node 518 via the “serves” edge534 to represent that the VAV represented by the VAV node 516 serves(e.g., heats or cools) the zone represented by the zone node 518. TheVAV node 520 is related to the zone node 524 via the “serves” edge 538to represent that the VAV represented by the VAV node 520 serves (e.g.,heats or cools) the zone represented by the zone node 524. The VAV node512 is related to the zone node 510 via the “serves” edge 528 torepresent that the VAV represented by the VAV node 512 serves (e.g.,heats or cools) the zone represented by the zone node 510.

Furthermore, the graph 529 includes an edge 533 related to a timeseriesnode 564. The timeseries node 564 can be information stored within thegraph 529 and/or can be information stored outside the graph 529 in adifferent database (e.g., a timeseries database). In some embodiments,the timeseries node 564 stores timeseries data (or any other type ofdata) for a data point of the VAV represented by the VAV node 516. Thedata of the timeseries node 564 can be aggregated and/or collectedtelemetry data of the timeseries node 564.

Furthermore, the graph 529 includes an edge 537 related to a timeseriesnode 566. The timeseries node 566 can be information stored within thegraph 529 and/or can be information stored outside the graph 529 in adifferent database (e.g., a timeseries database). In some embodiments,the timeseries node 566 stores timeseries data (or any other type ofdata) for a data point of the VAV represented by the VAV node 516. Thedata of the timeseries node 564 can be inferred information, e.g., datainferred by one of the artificial intelligence agents 570 and writteninto the timeseries node 564 by the artificial intelligence agent 570.In some embodiments, the timeseries 564 and/or 566 are stored in thegraph 529 but are stored as references to timeseries data stored in atimeseries database.

The twin manager 108 includes various software components. For example,the twin manager 108 includes a device management component 548 formanaging devices of a building. The twin manager 108 includes a tenantmanagement component 550 for managing various tenant subscriptions. Thetwin manager 108 includes an event routing component 552 for routingvarious events. The twin manager 108 includes an authentication andaccess component 554 for performing user and/or system authenticationand grating the user and/or system access to various spaces, pieces ofsoftware, devices, etc. The twin manager 108 includes a commandingcomponent 556 allowing a software application and/or user to sendcommands to physical devices. The twin manager 108 includes anentitlement component 558 that analyzes the entitlements of a userand/or system and grants the user and/or system abilities based on theentitlements. The twin manager 108 includes a telemetry component 560that can receive telemetry data from physical systems and/or devices andingest the telemetry data into the graph 529. Furthermore, the twinmanager 108 includes an integrations component 562 allowing the twinmanager 108 to integrate with other applications.

The twin manager 108 includes a gateway 506 and a twin connector 508.The gateway 506 can be configured to integrate with other systems andthe twin connector 508 can be configured to allow the gateway 506 tointegrate with the twin manager 108. The gateway 506 and/or the twinconnector 508 can receive an entitlement request 502 and/or an inferencerequest 504. The entitlement request 502 can be a request received froma system and/or a user requesting that an AI agent action be taken bythe AI agent 570. The entitlement request 502 can be checked againstentitlements for the system and/or user to verify that the actionrequested by the system and/or user is allowed for the user and/orsystem. The inference request 504 can be a request that the AI agent 570generates an inference, e.g., a projection of information, a predictionof a future data measurement, an extrapolated data value, etc.

The cloud platform 106 is shown to receive a manual entitlement request586. The request 586 can be received from a system, application, and/oruser device (e.g., from the applications 110, the building subsystems122, and/or the user device 176). The manual entitlement request 586 maybe a request for the AI agent 570 to perform an action, e.g., an actionthat the requesting system and/or user has an entitlement for. The cloudplatform 106 can receive the manual entitlement request 586 and checkthe manual entitlement request 586 against an entitlement database 584storing a set of entitlements to verify that the requesting system hasaccess to the user and/or system. The cloud platform 106, responsive tothe manual entitlement request 586 being approved, can create a job forthe AI agent 570 to perform. The created job can be added to a jobrequest topic 580 of a set of topics 578.

The job request topic 580 can be fed to AI agents 570. For example, thetopics 580 can be fanned out to various AI agents 570 based on the AIagent that each of the topics 580 pertains to (e.g., based on anidentifier that identifies an agent and is included in each job of thetopic 580). The AI agents 570 include a service client 572, a connector574, and a model 576. The model 576 can be loaded into the AI agent 570from a set of AI models stored in the AI model storage 568. The AI modelstorage 568 can store models for making energy load predictions for abuilding, weather forecasting models for predicting a weather forecast,action/decision models to take certain actions responsive to certainconditions being met, an occupancy model for predicting occupancy of aspace and/or a building, etc. The models of the AI model storage 568 canbe neural networks (e.g., convolutional neural networks, recurrentneural networks, deep learning networks, etc.), decision trees, supportvector machines, and/or any other type of artificial intelligence,machine learning, and/or deep learning category. In some embodiments,the models are rule based triggers and actions that include variousparameters for setting a condition and defining an action.

The AI agent 570 can include triggers 595 and actions 597. The triggers595 can be conditional rules that, when met, cause one or more of theactions 597. The triggers 595 can be executed based on informationstored in the graph 529 and/or data received from the buildingsubsystems 122. The actions 597 can be executed to determine commands,actions, and/or outputs. The output of the actions 597 can be stored inthe graph 529 and/or communicated to the building subsystems 122.

The AI agent 570 can include a service client 572 that causes aninstance of an AI agent to run. The instance can be hosted by theartificial intelligence service client 588. The client 588 can cause aclient instance 592 to run and communicate with the AI agent 570 via agateway 590. The client instance 592 can include a service application594 that interfaces with a core algorithm 598 via a functional interface596. The core algorithm 598 can run the model 576, e.g., train the model576 and/or use the model 576 to make inferences and/or predictions.

In some embodiments, the core algorithm 598 can be configured to performlearning based on the graph 529. In some embodiments, the core algorithm598 can read and/or analyze the nodes and relationships of the graph 529to make decisions. In some embodiments, the core algorithm 598 can beconfigured to use telemetry data (e.g., the timeseries data 564) fromthe graph 529 to make inferences on and/or perform model learning. Insome embodiments, the result of the inferences can be the timeseries566. In some embodiments, the timeseries 564 is an input into the model576 that predicts the timeseries 566.

In some embodiments, the core algorithm 598 can generate the timeseries566 as an inference for a data point, e.g., a prediction of values forthe data point at future times. The timeseries 564 may be actual datafor the data point. In this regard, the core algorithm 598 can learn andtrain by comparing the inferred data values against the true datavalues. In this regard, the model 576 can be trained by the corealgorithm 598 to improve the inferences made by the model 576.

Referring now to FIG. 6 , a process 600 for executing an artificialintelligence agent to infer and/or predict information is shown,according to an exemplary embodiment. The process 600 can be performedby the system 500 and/or components of the system 500. The process 600can be performed by the building data platform 100. Furthermore, theprocess 600 can be performed by any computing device described herein.

In step 602, the twin manager 108 receives information from a physicaldevice and stores the information, or a link to the information, in thegraph 529. For example, the telemetry component 560 can receivetelemetry data from physical devices, e.g., the building subsystems 122.The telemetry can be measured data values, a log of historical equipmentcommands, etc. The telemetry component 560 can store the receivedinformation in the graph 529 by relating a node storing the informationto a node representing the physical device. For example, the telemetrycomponent 560 can store timeseries data as the timeseries 566 along byidentifying that the physical device is a VAV represented by the VAVnode 516 and that an edge 537 relates the VAV node 516 to the timeseriesnode 566.

In step 604, the twin manager 108 and/or the cloud platform 106 receivesan indication to execute an artificial intelligence agent of an entityrepresented in the graph 529, the AI agent being associated with amodel. In some embodiments, the indication is created by a user andprovided via the user device 176. In some embodiments, the indication iscreated by an application, e.g., one of the applications 110. In someembodiments, the indication is a triggering event that triggers theagent and is received from the building subsystems 122 and/or anotheragent (e.g., an output of one agent fed into another agent).

In some embodiments, the AI agent is an agent for a specific entityrepresented in the graph 529. For example, the agent could be a VAVmaintenance agent configured to identify whether a VAV (e.g., a VAVrepresented by the nodes 512, 520, and/or 516) should have maintenanceperformed at a specific time. Another agent could be a floor occupantprediction agent that is configure to predict the occupancy of aparticular floor of a building, e.g., the floor represented by the floornode 522.

Responsive to receiving the indication, in step 606, the AI agent 570causes a client instance 592 to run the model 576 based on theinformation received in step 602. In some embodiments, the informationreceived in step 602 is provided directly to the AI agent 570. In someembodiments, the information is read from the graph 529 by the AI agent570.

In step 608, the AI agent 570 stores the inferred and/or predictedinformation in the graph 529 (or stores the inferred and/or predictedinformation in a separate data structure with a link to the graph 529).In some embodiments, the AI agent 570 identifies that the node thatrepresents the physical entity that the AI agent 570 inferred and/orpredicted information for, e.g., the VAV represented by the VAV 516. TheAI agent 570 can identify that the timeseries node 566 stores theinferred and/or predicted information by identifying the edge 537between the VAV node 516 and the timeseries node 566.

In step 610, the AI agent 570 can retrieve the inferred or predictedinformation from the graph 529 responsive to receiving an indication toexecute the model of the AI agent 570 of the inferred or predictedinformation, e.g., similar to the step 604. In step 612, the AI agent570 can execute one or more actions based on the inferred and/orpredicted information of the step 610 based the inferred and/orpredicted information retrieved from the graph 529. In some embodiments,the AI agent 570 executes the model 576 based on the inferred and/orpredicted information.

In step 614, the AI agent 570 can train the model 576 based on theinferred or predicted information read from the graph 529 and receivedactual values for the inferred or predicted information. In someembodiments, the AI agent 570 can train and update parameters of themodel 576. For example, the timeseries 564 may represent actual valuesfor a data point of the VAV represented by the VAV node 516. Thetimeseries 566 can be the inferred and/or predicted information. The AIagent 570 can compare the timeseries 564 and the timeseries 566 todetermine an error in the inferences and/or predictions of the model576. The error can be used by the model 576 to update and train themodel 576.

Referring now to FIG. 7 , a process 700 of an agent executing a triggerrule and an action rule is shown, according to an exemplary embodiment.The process 700 can be performed by the system 500 and/or components ofthe system 500. In some embodiments, the building data platform 100 canperform the process 700. Furthermore, the process 700 can be performedby any computing device described herein.

In step 702, the building data platform can store an agent 570 in a datastructure. The agent 570 can include a trigger rule indicating acondition for executing an action rule and an action rule indicating anaction to be performed responsive to the condition being met. In someembodiments, the model 576 includes, or can be replaced with, thetrigger rule and the action rule. The trigger rule and the action rulecan be logical statements and/or conditions that include parametervalues and/or create an output action.

In step 704, the agent 570 can receive information from at least one ofa physical device and/or from the graph 529. The information can begenerated by a physical device, e.g., the building subsystems 122. Thebuilding data platform 100 can, in some embodiments, receive theinformation from the physical device, ingest the information into thegraph 529, and the agent 570 can read the information from the graph529. In some embodiments, the agent 570 can check the information of thegraph 529 against a trigger rule at a set period.

In step 706, the agent 570 determines whether the information receivedin the step 704 causes the condition to be met. The agent 570 can applythe information to the trigger rule to determine whether the triggerrule is triggered, i.e., the condition of the trigger rule being met.

In step 708, the agent 570 can perform the action responsive to thecondition being met by the information determined in step 706. Theaction may cause a physical device to be operated or information be sentto another agent including another trigger rule and another action rule.In some embodiments, the action can be performed by executing the actionrule of the agent 570. The action rule can perform an action based onone or more parameter value of the action rule. In some embodiments, theaction output of the action rule can be sent directly to the physicaldevice, e.g., the building subsystems 122. In some embodiments, theaction output can be stored into the graph 529. Another operatingcomponent of the building data platform 100, e.g., the command processor136, can read the action from the graph 529 can communicate acorresponding command to the building subsystems 122.

Referring now to FIG. 8 , a system 800 where a clean air optimization(CAO) AI service 804 and an energy prediction model (EPM) AI service 806operate to make inferences and predictions based on data of a knowledgegraph 802 is shown, according to an exemplary embodiment. The knowledgegraph 802 includes various nodes and edges. The nodes may be the nodes808-842. The edges may be the edges 844-878.

The nodes may represent various entities of a building and/or buildings.The entities may be a campus, a building, a floor, a space, a zone, apiece of equipment, a person, a control point, a data measurement point,a sensor, an actuator, telemetry data, a piece of timeseries data, etc.The edges 844-878 can interrelate the nodes 808-842 to represent therelationships between the various entities of the building. The edges844-878 can be semantic language based edges 844-878. The edges caninclude words and/or phrases that represent the relationship. The wordsand/or phrases can include at least one predicate, in some cases.

The knowledge graph 802 includes a building node 836 representing abuilding. The building can include floors, represented by the buildingnode 836 being related to a floor 1 node 840 via an “hasPart” edge 870and the building node 836 being related to a floor 3 node 838 via a“feeds” edge 868. The building includes an energy prediction, e.g., avalue or a timeseries of values indicating energy usage of the building.This can be represented by the building node 836 being related to anenergy prediction node 830 via the edge 872.

The floor 1 includes zones, indicated by the floor 1 node 840 beingrelated to a zone1-1 node 808 via a “hasPart” edge 844 and the floor 1node 840 being related to a zone1-2 node 842 via a “hasPart” edge 845.Furthermore, the floor 1 can be fed by a particular AHU, AHU1. This isindicated by an AHU1 node 822 being related to the floor 1 node 840 viathe “feeds” edge 860. The zone1-2 can include a VAV1-2 that feeds air toit. This can be indicated by the VAV1-2 node 810 being related to thezone1-2 node 842 by the “feeds” node 862. The AHU1 can feed the VAV1-2,indicated by the AHU1 node 822 being related to the VAV1-2 node 810 bythe “feeds” edge 858.

An AHU 3 can feed air to the floor 3, indicated by the “AHU3” node 834being related to the “floor 3” node 838 by the “feeds” edge 866. The“AHU3” node 834 is related to a CAO inference 828 via an edge 874representing that the AHU has a clean air optimization inference thatcould be determined by the CAO AI service 804. The knowledge graph 802includes an AHU2 node 832. The AHU2 832 is related to a floor 2 node 841via a “feeds” edge 864 indicating that the AHU2 feeds air to the floor2. The AHU2 node 832 is related to a CAO inference 826 via the edge 876.The CAO inference 826 can indicate an inference made by the CAO AIservice 804 for the AHU2. The AHU1 822 is related to a CAO inference 824via edge 878. The CAO inference 824 can indicate a clean airoptimization inference made by the CAO AI service 804 for the AHU1.

The knowledge graph 802 includes a VAV1-1 node 812 indicating a VAV1-1.The VAV1-1 node 812 is related to the zone1-1 node 808 via a “feeds”edge 846 indicating that the VAV1-1 feeds air to the zone1-1. The AHU1can feed air to the VAV1-1 indicated by the AHU1 node 822 being relatedto the VAV1-1 node 812 via the “feeds” edge 856. The VAV1-1 node 812includes various points, e.g., a zone temperature point (represented bythe VAV1.ZN-T node 814) and a zone relative humidity point (representedby the VAV1.ZN-RH node 816). The VAV1-1 node 812 is related to theVAV1.ZN-T node 814 via the “hasPoint” edge 848. The VAV1-1 node 812 isrelated to the VAV1.ZN-RH node 816 via the “hasPoint” edge 854.

The VAV1.ZN-T point includes a timeseries node 818 representing and/orstoring a timeseries for the zone temperature, indicated by thetimeseries node 818 being related to the VAV1.ZN-T node 814 via the“hasTimeseriesID” node 850. The VAV1.ZN-RH point includes a timeseriesnode 820 representing and/or storing a timeseries for the zone humidity,indicated by the timeseries node 820 being related to the VAV1.ZN-RHnode 816 via the “hasTimeseriesID” node 852. In some embodiments, thetimeseries node 818 and the timeseries node 820 are identifiers of aparticular timeseries stored in a separate timeseries database, theidentifier uniquely identifying the location of the timeseries so asystem can consult the knowledge graph 802 and use the identifiers toretrieve the timeseries data from the separate timeseries database.

The system 800 includes a CAO AI service 804. The CAO AI service 804 canbe configured to identify timeseries that it needs to execute on. Forexample, if the CAO AI service 804 is executing for the AHU1, the CAO AIservice 804 could identify timeseries data linked to the AHU1. The CAOAI service 804 can generate CAO inferences, e.g., can infer idealsettings for clean air. The ideal settings could be an AHU supply airtemperature setpoint, an AHU minimum ventilation rate, etc. The idealsettings can be ingested into the knowledge graph 802, e.g., as the CAOinferences 824-830.

In some embodiments, the CAO AI service 804 (or an agent for the CAO AIservice 804) operates on behalf of a particular entity, e.g., the AHU 1.The CAO AI service 804 can generate inferences with data of the AHU 1,e.g., by identifying timeseries data of the AHU 1 by identifyingtimeseries nodes of the knowledge graph 802 via an edge. The inferencescan be ingested into the knowledge graph 802 by generating a new nodeand/or adding an edge between the new node and the node of the AHU 1,AHU 1 node 822. Similarly, the inferences can be added to the knowledgegraph 802 by updating an existing node related to the AHU 1 node 822 viaan existing edge. In some embodiments, the inferences of the CAO AIservice 804 can generate a recommendation, e.g., a control setting forimproving or optimizing air quality, which can be reviewed and approvedby a user via the user device 176.

The EPM AI service 806 can generate energy predictions for variousbuildings, spaces, or devices of a building, e.g., entities of theknowledge graph 802. For example, the EPM AI service 806 could predict afuture energy consumption level of the building 836, e.g., a futureenergy demand. The energy prediction can be a node 830 related to thebuilding node 836 via the edge 872. In some embodiments, the EPM AIservice 806 can generate the energy prediction node 830 responsive togenerating the future building energy consumption and cause the node 830to include a value for the future building energy consumption. The node830 can be added to the graph 802 and the edge 872 can be generated bythe EPM AI service 806 and added between the building node 836 and theenergy prediction 830.

In some embodiments, the energy prediction node 830 already existswithin the knowledge graph 802. In this example, the EPM AI service 806can identify the energy prediction node 830 by identifying an edge 872between the building 836 and the energy prediction node 830. The EPM AIservice 806 can then ingest the energy prediction into the node 830.

Referring now to FIG. 9 , a system 900 including a CAO AI agent 924 andan EPM AI agent 926 operating against the knowledge graph 802 togenerate inferences and predictions is shown, according to an exemplaryembodiment. The system 900 can be implemented on one or more processingcircuits, e.g., as instructions stored on one or more memory devices andexecuted on one or more processors. The memory devices and processorsmay be the same as or similar to the memory devices and processorsdescribed with reference to FIG. 1 .

The CAO AI agent 924 can operate on behalf of the CAO AI service 804.Similarly, the EPM AI agent 926 can operate on behalf of the EPM AIservice 806. Furthermore a service bus 914 can interface with the agent924 and/or the agent 926. A user can interface with the agents 924-926via the user device 176. The user can provide an entitlement request,e.g., a request that the user is entitled to make and can be verified bythe AI agent manager 916. The AI agent manager 916 can send an AI jobrequest based on a schedule to the service bus 914 based on theentitlement request. The service bus 914 can communicate the AI jobrequest to the appropriate agent and/or communicate results for the AIjob back to the user device 176.

In some embodiments, the CAO AI agent 924 can provide a request forgenerating an inference to the CAO AI service 804. The request caninclude data read from the knowledge graph 802, in some embodiments.

The CAO AI agent 924 includes a client 902, a schema translator 904, anda CAO client 906. The client 902 can be configured to interface with theknowledge graph 802, e.g., read data out of the knowledge graph 802. Theclient 902 can further ingest inferences back into the knowledge graph802. For example, the client 902 could identify timeseries nodes relatedto the AHU1 node 2622, e.g., timeseries nodes related to the AHU1 node2622 via one or more edges. The client 902 can then ingest the inferencemade by the CAO AI agent 924 into the knowledge graph 802.

The client 902 can provide data it reads from the knowledge graph 802 toa schema translator 904 that may translate the data into a specificformat in a specific schema that is appropriate for consumption by theCAO client 906 and/or the CAO AI service 804. The CAO client 906 can runone or more algorithms, software components, machine learning models,etc. to generate the inference and provide the inference to the client902. In some embodiments, the client 906 can interface with the EPM AIservice 806 and provide the translated data to the EPM AI service 806for generating an inference. The inference can be returned by the EPM AIservice 806 to the CAO client 906.

The EPM AI agent 926 can operate in a similar manner to the CAO AI agent924, in some embodiments. The client 908 can retrieve data from theknowledge graph 802 and provide the data to the schema translator 910.The schema translator 910 can translate the data into a readable formatby the CAO AI service 804 and can provide the data to the EPM client912. The EPM client 912 can provide the data along with a predictionrequest to the CAO AI service 804. The CAO AI service 804 can generatethe prediction and provide the prediction to the EPM client 912. The EPMclient 912 can provide the prediction to the client 908 and the client908 can ingest the prediction into the knowledge graph 802.

In some embodiments, the knowledge graph 802 includes data necessary forthe inferences and/or predictions that the agents 924 and 926 generate.For example, the knowledge graph 802 can store information such as thesize of a building, the number of floors of the building, the equipmentof each floor of the building, the square footage of each floor, squarefootage of each zone, ceiling heights, etc. The data can be stored asnodes in the knowledge graph 802 representing the physicalcharacteristics of the building. In some embodiments, the EPM AI agent926 makes the predictions based on the characteristic data of thebuilding and/or physical areas of the building.

Referring now to FIG. 10 , a system 1000 including the edge platform 102performing event enrichment at the edge platform 102 before the eventsare communicated to the cloud platform 106 is shown, according to anexemplary embodiment. The system 1000 includes the building subsystems122, the edge platform 102, the cloud platform 106, the applications110, and the twin manager 108. The edge platform 102 can receive eventsfrom the building subsystems 122 and enrich the events before passingthe events on to the cloud platform 106. Because the edge platform 102is located on-premises, e.g., on the edge, the events can be enrichedbefore being passed on to other cloud systems and/or used in edge basedanalytics run on the edge platform 102. In some embodiments, processors,memory devices, and/or networking devices of the edge platform 102 arelocated on-premises within a building.

The edge platform 102 can receive events from the building subsystems122. The events can be data packages describing an event that hasoccurred with a timestamp of when the event occurred. The events can beraw events that are composed of content that is emitted from a producingsystem. However, the event may not include any intent or knowledge ofthe system that consumes it. The event can be of a particular eventtype. An enrichment manager 1002 of the edge platform 102 can receivethe events from the building subsystems 122. The enrichment manager 1002can be the same as, or similar to, the enrichment manager 138.

The enrichment manager 1002 can enrich the events received from thebuilding subsystems 122 based on event context received and/or retrievedfrom a lite digital twin 1008 of the edge platform 102. For example, theenrichment manager 1002 can add entity and/or entity relationshipinformation associated with the event to the event to generate theenriched events 1004. The event enrichment can be the same as or similarto the enrichment described with referenced to FIGS. 1-3 and FIG. 8 .The enriched events 1004 can be an event with additional addedproperties or attributes that provide context regarding the event.

In some embodiments, the enrichment manager 1002 includes multiple eventstreams. The event streams can be data enrichment processing streams forparticular events and/or particular types of events. Each event streamcan be linked to a tenant and/or tenant subscription. Each event streamcan indicate one or more rules for enriching an event, e.g., anindication of the information to add to the event. In this regard, oneevent can be applied to multiple event streams and receive differentenrichments to generate multiple enriched events. Each enriched eventcan be provided to a different application or end system.

The edge platform 102 includes edge applications 1010. The edgeapplications 1010 can be similar to or the same as the applications 110.While the applications 110 may be run on a cloud system, the edgeapplications 1010 can be run locally on the edge platform 102. The edgeapplications 1010 can operate based on the enriched events 1004 and maynot need to consult a digital twin to acquire context regarding an eventsince the enriched events 1004 may already include the needed context.In some embodiments, the edge application 1010 performs analytics (e.g.,aggregation, data monitoring, etc.), control algorithms, etc. for thebuilding subsystems 122.

For example the edge applications 1010 can generate control decisionsfor the building subsystems 122 based on the enriched events 1004, e.g.,temperature setpoints for zones, fan speed settings for fans, ductpressure setpoints, ventilation commands, etc. In some embodiments, theedge applications 1010 include models, e.g., machine learning models forpredicting characteristics and/or conditions and/or for operating thebuilding subsystems 122. In some embodiments, the machine learning isperformed at the edge platform 102 which results in higher scores thanmachine learning performed in the cloud since a greater amount of datacan be collected faster and used for training at the edge.

In some embodiments, the enrichment manager 1002 only operates when thetwin manager 108 is not operating and enriching events. For example, theedge platform 102 can receive an indication that there is an error withcloud systems, e.g., network issues, computing issues, etc. In thisregard, the edge platform 102 can take over enriching the events withthe enrichment manager 1002 and operating on the events with the edgeapplications 1010. In this regard, the enrichment and applicationoperation can dynamically move between the edge platform 102 and thecloud platform 106. Furthermore, load balancing can be implemented sothat some events are enriched and operated on by edge applications 1010while other events are passed to the cloud platform 106 and/or the twinmanager 108 for enrichment and provided to the applications 110 foroperation.

In some embodiments, by performing enrichment at the edge platform 102,analytics can be performed at the edge platform 102 based on theenriched events. In this regard, lower latencies can be realized sinceanalytics and/or control algorithms can be performed quickly at the edgeplatform 102 and data does not need to be communicated to the cloud. Insome embodiments, the edge applications 1010 and/or machine learningmodels of the edge applications 1010 can be built in the cloud andcommunicated to the edge platform 102 and additional learning can beperformed at the edge platform 102.

The edge platform 102 includes the lite digital twin 1008. The litedigital twin 1008 can be a version of a digital twin 1011 of the twinmanager 108. The digital twins 1011 and/or 1008 can be virtualrepresentations of a building and/or the building subsystems 122 of thebuilding. The digital twin 1011 and/or the digital twin 1008 can be orcan include the graph projection database 162, e.g., one or more graphdata structures. The digital twin 1011 and/or the lite digital twin 1008can be the graphs shown in FIGS. 11-13 . In some embodiments, the litedigital twin 1008 is a projection that does not include all nodes andedges of a full projection graph. The lite digital twin 1008 may onlyinclude the nodes or edges necessary for enriching the events and can bebuilt on projection rules that define the information needed that willbe used to enrich the events.

In some embodiments, the lite digital twin 1008 can be synchronized, inwhole or in part, with the digital twin 1011. The lite digital twin 1008can include less information than the digital twin 1011, e.g., lessnodes or edges. The lite digital twin 1008 may only include the nodesand/or edges necessary for enriching events of the building subsystems122. In some embodiments, changes or updates to the digital twin 1011can be synchronized to the lite digital twin 1008 through a change feedof change feed events. The change feed can indicate additions, removals,and/or reconfigurations of nodes or edges to the graph projectiondatabase 162. Each change feed event can indicate one update to thedigital twin 1011.

A digital twin updater 1006 can receive the events of the change feedfrom the change feed generator 152 and update the lite digital twin 1008based on each change feed event. The updates made to the lite digitaltwin 1008 can be the same updates as indicated by the events of thechange feed. In some embodiments, the digital twin updater 1006 canupdate the lite digital twin 1008 to only include the nodes and edgesnecessary for enrichment of the events, and thus include less nodes andedges than the digital twin 1011.

In some embodiments, the digital twin updater 1006 filters out changefeed events if the change feed events do not pertain to informationneeded to enrich the events. In this regard, the digital twin updater1006 can store a list of information needed for enrichment, e.g., thedigital twin updater 1006 can include all event subscriptions orenrichment rules. The digital twin updater 1006 can determine whether achange feed event updates information pertaining to event enrichment andonly update the lite digital twin 1008 responsive to determining thatthe change feed event updates information needed for enrichment. In someembodiments, when a new event subscription and/or new enrichment rule iscreated, the digital twin updater 1006 can communicate with the digitaltwin 1011 to retrieve noes or edges needed for the new eventsubscription and/or enrichment rules.

Referring now to FIG. 11 , a building graph 1100 divided and distributedacross a cloud system and an edge system is shown, according to anexemplary embodiment. The building graph 1100 can form a hybridknowledge graph (e.g., a graph data structure) which may be part of, orform, a digital twin. The hybridization of the building graph 1100 canallow for various applications to run against the building graph 1100 onedge systems, in cloud systems, or in a combination of edge systems andcloud systems. In some embodiments, the building graph 1100 can bedivided up based on space or building. For example, edge systems of onespace might have a building graph for the one space while edge systemsfor another space might have a building graph for the other space. Insome embodiments, the building graph 1100 is divided up based on theoperational requirements of various edge systems and cloud systems,e.g., a portion of the building graph 1100 may be stored and operated oneach edge system or cloud system that allows each edge system or cloudsystem to perform its operations.

The building graph 1100 includes a cloud building graph 1102 and an edgebuilding graph 1104. The cloud building graph 1102 can be stored by acloud system, in some embodiments. The edge building graph 1104 can bestored by an edge system, in some embodiments, examples of the cloudsystem and the edge system are provided in FIG. 12 . The building graphs1102 and 1104 can be the same as, or similar to, the building graphsdescribed in FIGS. 1-5 and 8 .

By dividing the building graph 1100 into parts (e.g., the graph 1102 andthe graph 1104) and distributing the parts across various locationsprovides privacy and security advantages. Because the building graph1100 is divided and distributed, for a hacker or other entity to gainaccess to the entire building graph 1100, multiple separate devices (andthe security systems of each device) may need to first be compromised.Requiring multiple different devices to be compromised before the entirebuilding graph 1100 is compromised can increase the difficulty ofcompromising the building graph 1100. Furthermore, by distributing partsof the building graph 1100, privacy can be established. In someembodiments, the information of each graph being stored separately canallow for sensitive information to reside in one device with lesssensitive information residing in a different device. This allows forthe location of information to be controlled to make sure that privateinformation is only stored in locations that a user or entity desires(e.g., locations with high security).

The cloud building graph 1102 and the edge building 1104 include variousnodes, i.e., nodes 1106-1134. The cloud building graphs 1102 and 1104further includes edges connecting the various nodes 1106-1134, e.g.,edges 1136-1174. The nodes 1106-1134 can represent buildings, spaces,systems, devices, people, state data, timeseries data, sensormeasurements, event data, inferred information, event streams, and/orany other type of data. The edges 1136-1174 can represent directional orbidirectional relationships between the nodes 1106-1134. In someembodiments, the edges 1136-1174 include semantic language basedrelationships that include one or more predicates, nouns, and/orprepositions that describe a relationship type. In some embodiments, thecloud building graph 1102 and/or the edge building graph 1104 areformatted according to a specific schema, e.g., the BRICK schema. Insome embodiments, the nodes and edges stored by the cloud building graph1102 and the edge building graph 1104 are different. In someembodiments, there is overlap between the nodes and edges stored by thecloud building graph 1102 and the edge building graph 1104.

In some embodiments, the cloud building graph 1102 includes a buildingnode 1122. The building node 1122 can represent a particular building,e.g., a school, a hospital, a commercial business office, a high rise,an apartment, etc. The cloud building graph 1102 includes a floor 2 node1124 related to the building node 1122 by a “hasPart” node 1158. Thisindicates that the building has a second floor, floor 2. The buildingnode 1122 is related to a floor 3 node 1120 by a “hasPart” edge 1156.This indicates that the building includes a third floor, floor 3.Furthermore, the building node 1122 is related to a floor 1 node 1118 bya “hasPart” edge 1152. This indicates that the building has a firstfloor, floor 1.

The floor 1 node 1118 is related to a zone1-1 node 1116 by a “hasPart”edge 1150. This indicates that the first floor, floor 1, has a firstzone, zone1-1. The zone1-1 node 1116 is related to a VAV1-2 node 1114 bya “feeds” edge 1148. This indicates that a particular VAV, VAV1-2,operates to feed air to the zone1-1. The VAV1-2 is associated with twodifferent points and timeseries. The VAV1-2 node 1114 is related by a“hasPoint” edge 1140 to a zone temperature point, VAV1.ZN.T node 1110.The VAV1.ZN.T node 1110 is related by a “hasTimeseries” edge 1136 to atimeseries node 1106. This indicates that the zone temperature pointincludes an associated timeseries of zone temperature measurements madeby the VAV1-2 or another system associated with the zone1-1 (e.g., asensor or thermostat). The VAV1-2 node 1114 is related by a “hasPoint”edge 1142 to a zone humidity point, VAV1.ZN.RH node 1112. The VAV1.ZN.RHnode 1112 is related by a “hasTimeseries” edge 1138 to a timeseries node1108. This indicates that the zone humidity point includes an associatedtimeseries of zone humidity measurements made by the VAV1-2 or anothersystem associated with the zone1-1 (e.g., a sensor or thermostat). Insome embodiments, the timeseries node 1106 and/or the timeseries node1108 (or the timeseries data associated with the nodes) are stored in aseparate timeseries database and related to the graph 1102 by anidentifier.

The edge building graph 1104 includes an AHU1 node 1128 representing anAHU of the building. The AHU1 node 1128 is related to a VAV1-2 node 1130by a “feeds” edge 1170. This indicates that the AHU1 feeds air to theVAV1-2. The VAV1-2 node 1130 is related to a zone1-2 node 1132 by a“feeds” edge 1172. This indicates that the VAV1-2 node 1130 feeds air tothe zone1-2. The AHU1 node 1128 is related by a “hasA” edge 1174 to anartificial intelligence (AI) inference event stream node 1134. The AIinference event stream node 1134 can store (or include an identifierlinking to a separate data storage system) inferred events generated byan AI service. The event stream could be inferred weather conditions,inferred occupancy, inferred comfort settings for the AHU, etc. A systemthat runs the AHU1 can use the event stream to make operationaldecisions (e.g., determine heating levels, cooling levels, air pressuresettings, fan levels, air mixture levels, etc.).

The cloud building graph 1102 and the edge building graph 1104 may bothdescribe elements of the same building, in some embodiments. Therefore,the cloud building graph 1102 and the edge building graph 1104 can berelated together. The interrelationships can enable the cloud buildinggraph 1100 to be split apart but for queries or other actions to stillconsider the entire graph 1100, in some embodiments.

In some embodiments, an edge 1 node 1126 can be stored by the cloudbuilding graph 1102 and/or the edge building graph 1104. The edge 1 node1126 may represent the edge building graph 1104. Similarly, another nodemight describe the cloud building graph 1102 (e.g., as shown in FIG. 12). The graphs 1102 and/or 1104 can include edges that relate nodes ofeach graph 1102 and/or 1104 to the node 1126. Relating a node to thenode 1126 may indicate that an object of the relationship exists inanother graph, e.g., the graph indicated by the edge 1 node 1126. Forexample, if the edges are in the form of triples with subjects,predicates, and objects, relating a node (subject) via an edge(predicate) to the edge 1 node 1126 may indicate that the object for therelationship exists in another graph (e.g., a graph indicated by thenode 1126). Similarly, if the edge 1 node 1126 is the subject of atriple, this may indicate that the subject of the triple is stored inanother graph, e.g., the graph indicated by the edge 1 node 1126.

The VAV1-2 node 1114 is related to the AHU1 node 1128 via an edge“Edge1[AHU1]->feeds::Cloud1[VAV1-2]” 1144 between the edge 1 node 1126and the VAV1-2 node 1114 and the edge“Edge1[AHU1]->feeds::Cloud1[VAV1-2]” edge 1164. The edges 1144 and 1164can indicate that the AHU1 node 1128 (the subject) feeds (the predicate)the VAV1-2 node 1114 (object). The edges 1144 and 1164 can each identifythe AHU1 node by name, provide an indication of which graph the AHU1node is stored, e.g., “Edge1[AHU1]” provide an indication of thedirection of the relationship “->” (from the AHU1 to the VAV1-2) andindicate the location of the VAV1-2 node 1114 “Cloud1[VAV1-2].” The “::”symbol can indicate a separation between graphs, e.g., a separationbetween the Edge1 graph (the graph 1104) and the Cloud1 graph (the graph1102). The location of the “AHU1” on the left side of the arrow->canindicate that the AHU1 is the subject of the triple while the locationof the VAV1-2 on the right side of the arrow “->” can indicate that theVAV1-2 is the object of the triple. Reversing the arrow “->” to “<-”would indicate a reverse of the subject and object, in some embodiments.Furthermore, an arrow such as “<->” would indicate a bidirectionalrelationship where each node is both a subject and object, in someembodiments. The “feeds” portion of the edges 1144 and 1164 can indicatethe semantic type (e.g., “isPartOf,” “includes,” etc.) of the edges 1144and 1164.

While a particular syntax is provided in FIG. 11 for the edges relatingnodes of different graphs, various other syntaxes could be used torelate the information. Furthermore, the relation of information could,in some embodiments, be stored within the nodes or edges of the graph1100 itself and/or within a separate lookup table. In some embodiments,the lookup table could relate the graph names “Cloud1” and/or “Edge1” tophysical devices that store the respective graphs, e.g., to systemidentifiers, to network addresses, to cryptographic communication codes,etc. In some embodiments, the lookup table can use obfuscation to hideidentifying information of the devices storing the graphs 1102 and 1104.

The “Edge1[AHU]->feeds Cloud[Floor1]” edge 1146 between the edge 1 node1126 and the floor 1 node 118 and the “Edge1[AHU1]->feedsCloud1[Floor1]” edge 1166 between the AHU1 node 1128 and the edge1 node1126 can indicate that the AHU 1 feeds air to the floor 1. The“Cloud1[Floor1]->hasPart Edge1[Zone1-2]” edge 1154 between the floor 1node 1118 and the edge 1 node 1126 and the “Cloud1[Floor1]->hasPartEdge1[Zone1-2]” edge 1168 between the edge 1 node 1126 and the zone1-2node 1132 can indicate that the floor 1 has the zone1-2. The“Edge1[AHU1]->feeds Cloud1[Floor2]” edge 1160 between the edge 1 node1126 and the floor 2 node 1124 and the “Edge1[AHU1]->feedsCloud1[Floor2]” edge 1162 between the edge 1 node 1126 and the AHU 1node 1128 can indicate that the AHU1 feeds the floor 2.

By dividing the building graph 1100 into the graphs 1102 and 1104 butincluding the edges 1144-1146, 1154, 1160, 1162, 1164, 1166, and 1168which link the graphs 1102 and 1104 together, queries can be executedwhich traverse the entire building graph 1100 without requiring thequeries to specify which graph is being queried. For example, if asystem provides a query for all parts of the floor 1, the query responsecan include the zone1-1 and the zone1-2, even though the zone 1-2 isstored in a graph separate from the floor 1. The query responding systemcan identify and retrieve an indication of the zone 1-2 based ontraversing edges across the graphs 1102 and 1104, e.g., the edges 1154and 1168. In some embodiments, a first system that is associated withthe cloud building graph 1102 (e.g., stores the graph 1102) can completea first portion of the query (e.g., identify the zone1-1) use the edge1154 to identify that a second result for the query is stored in thegraph 1104, and second the query to a second system associated with theedge building graph 1104. The second system can complete the query(e.g., identify the zone 1-2 node 1132 based on the edge 1168 or anyother pieces of information in the graph 1104), and send a response tothe first system.

The first system can then combine the results together and generate aquery response based on the combined results. One or more applicationprogramming interfaces (APIs) can provide an interface for querying thegraphs 1102-1104. Because the graphs 1102 and 1104 are linked togethervia edges, even though they may be stored in separate data storagedevices, on different devices connected through one or more networks,etc., the queries provided to the API can be agnostic to (e.g., notinclude) information identifying where (or in what graph) the queriedinformation resides, how to break down the queries into sub-parts,and/or how to route the queries. The API can break a query into variousparts for each of the graphs 1102-1104 and route the queries to variousdevices to query the graphs stored by each device. One example ofbreaking a query down into sub-parts to produce a query result is foundin U.S. patent application Ser. No. 15/409,489 filed Jan. 18, 2017 (nowU.S. Pat. No. 10,480,804), the entirety of which is incorporated byreference herein.

In some embodiments, instead of including timeseries nodes, e.g., thenode 1110 and/or the node 1112, the graph 1100 can store events,timeseries, and/or other data samples linked directly with an entitynode (e.g., equipment, space, person, etc.). For example, a single edgemay connect the data sample node directly to the entity node. In someembodiments, each entity, whether equipment, space, or a point, caninclude an edge to an event metadata node. The event metadata node candescribe the type of data samples that can be associated with thatentity. The data samples can be formatted according to a format definedby the metadata node but linked directly with the entity generatingthem, or in the case of inferred events, applied to them.

For example, if there is a meeting that gets booked in a conferenceroom, the event describing that meeting room booking would be associateddirectly with the conference room entity itself. Furthermore, an eventmetadata entity can also be linked to a node representing the meetingroom which describes a “MeetingRequest” event and its format. Thismetadata entity may describe the types of events that can be associatedwith that conference room entity.

Referring now to FIG. 12 , a system 1200 is shown including the twinmanager 108 and an edge device 1204 storing the building graph 1100divided and distributed across the twin manager 108 and the edge device1204, according to an exemplary embodiment. The twin manager 108 can bea cloud based device that includes the memory device(s) 150 and theprocessor(s) 148. The one or more memory device(s) 150 can store thecloud building graph 1102, the cloud agents 1206, the device-graphlookup table 1220, and/or any instructions that can be executed by theprocessor(s) 140 to store, manage, execute against, etc. the cloudbuilding graph 1102 and/or the edge building graph 1104.

The edge device 1204 includes processor(s) 1210 and the memory device(s)1212. The processor(s) 1210 and the memory device(s) 1212 can be similarto, or be the same type as, the processor(s) 148 and the memorydevice(s) 150. The edge device 1204 can be a device located on the edge,e.g., on-premises within a building, at a particular environment, in avehicle, etc. The edge device 1204 could be a building controller, avehicle computing system, a personal computer, an equipment controller,a METASYS ADX server, a building server, a fire response system, anaccess control system, a video surveillance system, etc. In someembodiments, the edge device 1204 can be a server of a cellular tower.For example, the edge device 1204 could be a 5G Mobile Edge Computing(MEC) system. 5G MEC systems can allow for communication with edgedevices and processing for edge devices while only requiringcommunication via 5G, i.e., without requiring any other network hops(e.g., network hops across a core network, the Internet, etc.). 5G MECis described in U.S. patent Ser. No. 17/221,064 filed Apr. 2, 2021, theentirety of which is incorporated by reference herein.

As an example, in some embodiments, the edge device 1204 is a fieldcontroller or an equipment controller. The controller could collect andstore historical equipment data which can be stored in, or linked to, abuilding graph stored by the controller. The controller can further runvarious agents to perform fault detection and diagnosis for theequipment. The agents can run against the historical data, the graphstored by the controller, or another graph stored in a cloud or otheredge system that includes information relating to making a faultdetection for the equipment. For example, the other graphs could storeinformation about the spaces, people, or equipment that might provideinformation that the controller could use in making a fault detectionand/or diagnosis. For example, the information might indicate how othersimilar pieces of equipment are operating, the environmental data ofvarious spaces controlled by the equipment, etc.

In some embodiments, the distributed digital twin can store both theportion of the building graph and the historical data necessary for theagents of the digital twin to execute. For example, the edge device 1204could store a historical database, e.g., a timeseries database. In someembodiments, the timeseries data can be stored in the timeseriesdatabase with a link to a node of the edge building graph 1104. In thisregard, the edge device 1204 could receive sensor measurements from thesensor devices 1214 and/or actuator feedback from the actuator devices1216 and store the data, via a device manager 1218 of the edge device1204, in the graph 1104 and/or in a historical database of the edgedevice 1204. In some embodiments, the device manager 1218 can store alink in a node of the edge building graph 1104 that links to a locationin a separate database that aggregates the received sensor and/oractuator data.

In some embodiments, for a campus of multiple buildings or an entitywith multiple building sites, one server could reside at each building.Each of the servers could store a building graph for the specificbuilding that the servers are located in. The cloud server could store abackup graph of all of the graphs stored at each of the individualservers. In some embodiments, the cloud server could include a graphstoring other high level information that is related to the informationof one or more of the graphs of the servers. The servers could, in someembodiments, push gathered building data up to the cloud for the cloudto run algorithms against. In some embodiments, the servers could retainthe gathered building data and run algorithms for the respectivebuildings locally.

The twin manager 108 includes a device-graph lookup table while the edgedevice 1204 includes a device-graph lookup table 1222. The tables 1220and/or 1222 can be tables that link a graph name to a specific device.The tables 1222 and/or 1220 can allow the interface 1224 of the twinmanager 108 and/or the interface 1226 of the edge device 1204 tocommunicate with each other via the network 104. For example, thecommunication may be querying the graphs 1102 and/or 1104. Theinterfaces 1224 and/or 1226 can be circuits and/or pieces of software(e.g., API code) that handles communication, queries, commands,questions, etc. between the twin manager 108 and the edge device 1204.

In some cases, the interfaces 1224 and/or 1226 are shepherding agentsthat coordinate the local storage of a graph and/or agent betweenmultiple devices. In some embodiments, the shepherding agents cancoordinate communication between edge and cloud systems such that agateway layer (e.g., the edge platform 102) is not needed to facilitatecommunication between the cloud (e.g., the cloud platform 106 and/or thetwin manager 108) and edge devices (e.g., the building subsystems 122).The messaging and/or routing mechanisms provided by the interfaces 1224and/or 1226 can allow for business logic, control algorithms, artificialintelligence (AI) models, machine learning (ML) models, etc. that mightnormally run in the cloud to be run in various edge or cloud systems.

The device-graph lookup table 1220 and/or the device-graph lookup table1222 can link graph names of the graphs 1102 and/or 1104 to deviceidentifiers and/or communication addresses of the twin manager 108and/or edge device 1204. An example lookup table could be:

TABLE 1 Graph Device Internet Protocol MAC Name Identifier (IP) AddressAddress Cloud1 Cloud Server 84.15.186.115 00-17-FC-3F-FF-FF Cloud2Remote Computing 84.15.184.60 00-13-DD-F5-AB-F5 System Edge1 BuildingController 192.168.1.16 00-16-23-FF-44-25 Edge2 AHU Controller192.168.1.16 00-16-FC-22-56-21 Edge3 Data Collector 192.0.2.100-13-CA-44-21-89 Edge4 Local Server 192.0.2.1 00-19-FC-39-A6-99

Furthermore, each of the twin manager 108 and the edge device 1204 canstore and execute agents, e.g., the twin manager 108 includes cloudagents 1206 while the edge device 1204 includes edge agents 1208. Theagents 1206 and 1208 can be the same as, or similar to, the agentsdescribed in FIGS. 5-9 . By running agents on various cloud and/or edgedevices and/or by storing the parts of a building graph across thevarious cloud and/or edge devices can allow for a digital twin (ordigital twins) to be distributed across various cloud and/or edgedevices. By having agents running against parts of the graph stored onthe various cloud and/or edge devices can allow for digital twincomputing and/or storage to co-exist at the same location where thecomputations are being used, providing autonomous executioncapabilities. For example, if a controller for an AHU stores a portionof a building graph describing the AHU and an agent stored on thecontroller provides algorithms for running the AHU, the AHU controllercan run a digital twin for controlling the AHU through the agent and thebuilding graph stored by the AHU. This localizes the storage andexecution of a digital twin at edge devices.

This architecture shown in FIG. 12 also allow for flexibility of wherethe digital twin computations reside (e.g., on various clouds and/oredge devices). The architecture allows digital twin computations to notbe co-located with the a cloud platform, e.g., the cloud platform 106and/or the twin manager 108. Because the agents and graph can be storedlocally with the edge device 1204, this can result in faster computingand/or control decisions since the computations are performed at theedge instead of requiring the edge device 1204 to wait for communicationover the network 104 with the twin manager 108.

In some embodiments, one or multiple edge devices could store an edgegraph that is not utilized unless a connection to a cloud system isoffline and/or the cloud system is not operating properly. In thisregard, the edge graph could be in a dormant mode where the edge devicesstore and/or maintain the graph but do not execute any applicationsagainst the graph, e.g., run a digital twin at the edge. The dormantgraph could provide redundancy with the graph stored in the cloud system(e.g., include at least some of the same nodes and edges). The edgedevices can perform operations based on a digital twin running in thecloud system. However if the edge devices become disconnected from thecloud system or the cloud system goes offline, edge systems can run anedge digital twin based on the edge graphs stored by the edge systems,e.g., “wake up” the edge digital twin.

Referring now to FIG. 13 , the distributed building graph 1100 generatedacross the twin manager 108 and an edge device 1204 during an onboardingprocess is shown, according to an exemplary embodiment. The edge device1204, the twin manager 108, and the building controller 1306 canconstruct the building graph 1100 in a distributed manner. The edgedevice 1204, the twin manager 108, and the building controller 1306include onboarding tools for constructing the graph, e.g., onboardingtool 1304, onboarding tool 1308, and onboarding tool 1312.

The onboarding tools can build the building graph 1100 in a piecemealmanner from the various device that the onboarding tools reside. Whilethe building graph is constructed, each edge system can identify whichpieces of the graph should be stored locally, e.g., which pieces theedge system needs to execute and which pieces of the constructed graphshould be pushed to the cloud. The edge systems can further identifywhich portions of the graph to keep locally based on privacy. In somecases, the portions of the building graph that are retained locally atthe edge can be linked via one or more nodes or edges with otherportions of the building graphs stored by the other edge systems and/orcloud systems.

In some embodiments, the onboarding tool 1308 of the twin manager 108 ispushed data collected by the edge device 1204 and data collected by thebuilding controller 1306. The twin manager 108 (e.g., via the onboardingtool 1308) can generate a graph based on all of the data received. Thetwin manager 108 can make decisions of what portions of the graph shouldbe pushed to the edge device 1204 and the building controller 1306. Insome embodiments, each onboarding tool 1304, 1308, and 1312 locallybuilds a graph to be stored locally on each of the edge device 1204, thetwin manager 108, and the building controller 1306. Similarly, in someembodiments, each edge device can identify what agents the edge deviceneeds to execute to operate the equipment managed by the edge device.The edge devices can retrieve the agent from the twin manager 108, insome embodiments. In some embodiments, the twin manager 108 can analyzethe graph of each edge device (or a complete graph stored by the twinmanager 108) and determine what agents to push to the edge devices.

In some embodiments, the onboarding tools 1304, 1308, and 1312 cancontinue managing and updating the graphs stored on the edge device1204, the twin manager 108, and the building controller 1306respectively. As devices of the building change (which may beinfrequent) the onboarding tools 1304, 1308, and 1312 can performupdates to the various graphs and maintain consistent linkages acrossthe various graphs.

In FIG. 13 , the building controller manages an AHU controller 1322 anda VAV1-2 controller 1316. The AHU controller 1322 communicates withvarious AHU sensors 1324 and AHU actuators 1326. The VAV1-2 controllercommunicates with VAV sensors 1318 and VAV actuators 1320. Theonboarding tool 1304 can receive metadata from the AHU controller 1322and the metadata from the VAV1-2 controller 1316 defining the AHUsensors 1324, the AHU actuators 1326, the VAV sensors 1318, and the VAVactuators 1320. The onboarding tool 1304 can analyze the metadata toconstruct the edge building graph 1104.

The onboarding tool 1304 can perform various data analysis techniques togenerate the edge building graph 1104 from the metadata, e.g., thetechniques described in U.S. patent Ser. No. 16/885,959 filed May 28,2020, U.S. patent Ser. No. 16/885,968 filed May 28, 2020, U.S. patentSer. No. 16/663,623 filed Oct. 25, 2019, and U.S. patent Ser. No.16/722,439 filed Dec. 20, 2019, the entirety of each of which areincorporated by reference herein.

Furthermore, the onboarding tool 1304 can build the edge building graph1104 based on information received from the twin manager 108 and/or thebuilding controller 1306. For example, the onboarding tool 1312, whileusing data to build an edge building graph 1310 for the buildingcontroller 1306, can communicate the data to the twin manager 108 and/orthe edge device 1204. In some embodiments, the twin manager 108 cancommunicate metadata received from the building controller 1306 to theedge device 1204.

In some embodiments, the data received by the edge device 1204 from thetwin manager 108 is data describing the VAV1-1 controller 1314 thatcommunicates with the building controller 1306. The data can provide anindication of the VAV1-1, an indication that the floor 1 and the floor2are fed by AHU1, and an indication that the zone1-2 is part of thefloor1. The onboarding tool 1304 can use the data to generate the edges1162-1168.

Referring now to FIG. 14 , a process 1400 of querying a building graphdivided into multiple building graphs distributed across cloud and edgesystems is shown, according to an exemplary embodiment. The process 1400can be performed by the twin manager 108 and the edge device 1204. Theprocess 1400 can be performed by one or more edge systems and/or one ormore cloud systems. Furthermore, any computing device or group ofcomputing devices can perform the process 1400.

In step 1402, a system can receive a query for information of thebuilding graph 1100 where the building graph 1100 is divided intomultiple building graphs (e.g., the cloud building graph 1102 and theedge building graph 1104) distributed across multiple device (e.g., thetwin manager 108 and/or the edge device 1204). In some embodiments, thequery is an agent query generated by an agent, e.g., the cloud agents1206 or the edge agents 1208. The agent queries can be generated by theagents responsive to the agent identifying that it requires informationnot stored in a graph that the agent has direct access to (e.g., thecloud agents 1206 have direct access to the cloud building graph 1102.).In some embodiments, the queries are generated by applications (theapplications 110) that require some piece of information. In someembodiments, the queries are received, handled, and answered by theinterfaces 1224 and 1226.

In step 1404, the system can query a first building graph of thebuilding graphs for the information and identify that at least a portionof the information is stored in a second building graph. For example,the interface 1224 could query the cloud building graph 1102 forinformation. In some embodiments, the interface 1224 retrieves at leasta portion of the information from the cloud building graph 1102 to bereturned in response to the query. However, the interface 1224 mayfurther identify, based on the edges 1144, 1146, 1154, 1160, 1162, 1164,1166, and/or 1168, that the information (or a portion of theinformation) needed to respond to the query is stored in the edgebuilding graph 1104.

For example, if the query is for zones controlled by a VAV, theinterface 1224 can identify the zone1-1 node 1116 and identify that thezone1-1 1116 is fed by the VAV1-2 1114. Furthermore, the interface 1224can identify that the floor 1 node 1118 has a zone1-2 via edge 1154 andidentify based on the edge 1154 being related to the edge1 node 1126,the information describing the zone1-2 is in the edge building graph1104.

In step 1406, the system can communicate the query to at least one ofthe cloud system or the edge system that stores the second buildinggraph. For example, the interface 1226 may communicate a query to theinterface 1224 for the interface 1224 to generate a result based on.Similarly, the interface 1224 may communicate a query to the interface1226 for the interface 1226 to generate a result based on.

Continuing the previous example, responsive to identifying that thebuilding graph 1104 potentially stores information that should bereturned in the query for zones controlled by a VAV, in the step 1406the system, e.g., the interface 1224 can communicate the query to theinterface 1226. The interface 1224 may identify, based on thedevice-graph lookup table 1220 that the edge device 1204 stores the“Edge1” graph (e.g., the edge building graph 1104), the “Edge1” graphindicated by the edge 1154. The interface 1226 can query the edgebuilding graph 1104 for zones controlled by VAVs.

In step 1408, the system can query the second building graph based onthe query to identify the information and receive the information basedon the query. Again, continuing the previous example, the interface 1226can communicate the result of the query of the edge building graph 1104back to the interface 1224. The interface 1224 can compose a response(e.g., combine results from the graph 1102 and/or the graph 1104 orinclude results of only the graph 1102 and/or the graph 1104). Theresponse can be returned by the interface 1224 to the requesting system,e.g., the cloud agents 1206, applications, a user device, etc.

Referring now to FIG. 15 , a process 1500 of querying a building graphdivided into multiple building graphs distributed across cloud and edgesystems by an agent, and ingesting information back into the buildinggraph by the agent is shown, according to an exemplary embodiment. Theprocess 1500 can be performed by the twin manager 108 and the edgedevice 1204. The process 1500 can be performed by one or more edgesystems and/or one or more cloud systems. Furthermore, any computingdevice or group of computing devices can perform the process 1500.

In step 1502, an agent of the edge agents 1208 of the edge device 1204can query the building graph 1100 divided into multiple building graphs(e.g., the cloud building graph 1102 and the edge building graph 1104)and distributed across the cloud system (e.g., the twin manager 108) andthe edge device (e.g., the edge device 1204) for information. Theinformation can be information that the agent requires to performoperations, e.g., infer information, generate control decisions, run atemperature control algorithm, run an air quality algorithm, etc. Insome embodiments, the agent queries the graphs 1102 and 1104 byproviding the query to the interface 1226. The interface 1226 can runthe query, generate the query response, and provide the query responseback to the agent.

In step 1504, the agent can receive first information from the firstbuilding graph stored by the cloud system and second information from asecond building graph stored by the edge system. In some embodiments,the interface 1226 can compose a response including the firstinformation and the second information and return the response to theagent. The cross-graph query can be the query described in the process1400 of FIG. 14 .

In step 1506, the agent performs one or more operations to deriveinformation based on the first information and the second informationreceived in the step 1504. In some embodiments, the agent may performartificial intelligence (AI) based analysis to generate an event stream.The event stream may indicate a schedule of AI settings indicating thetimes at which settings should change. In step 1508, the agent caningest the information derived in the step 1506 into the first buildinggraph or the second building graph. For example, the agent could ingestthe AI inference event stream into the node 1134. In some embodiments,the device manager 1218 and/or the agent can push the settings to theAHU (e.g., an actuator of the AHU such as the actuator device 1216) tooperate the AHU to control environmental conditions of a building (e.g.,temperature, humidity, air quality, etc.).

Referring now to FIG. 16 , a process 1600 is shown of querying abuilding graph divided into multiple graphs distributed across a cloudsystem and an edge platform and using information queried from thebuilding graph to perform one or more operations, according to anexemplary embodiment. The process 1600 can be performed by the twinmanager 108 and the edge device 1204. The process 1600 can be performedby one or more edge systems and/or one or more cloud systems.Furthermore, any computing device or group of computing devices canperform the process 1600.

In step 1602, a system (e.g., the twin manager 108 and/or the edgedevice 1204) can query the building graph 1100 for information, thebuilding graph 1100 divided into multiple building graphs distributedacross a cloud system and an edge system, wherein one or more nodes oredges of a first graph stored by the edge system link the first buildinggraph to a second building graph stored by another edge system or thecloud system. In some embodiments, the system performing the query canbe an edge system, the cloud system, etc. In some embodiments, the querycan be made across multiple graphs based on the edges that connect thegraphs, e.g., the edges 1144, 1146, 1154, 1160, and/or 1162-1168. Insome embodiments, the system can identify which graph to queryinformation from based on how the edges link the various graphs. Thequery can be performed across the building graphs as described in theprocess 1400 by FIG. 14 .

In step 1604, the system can receive the information from the buildinggraph of the cloud system and/or the edge system. For example, the edgedevice 1204 could receive information of the edge building graph 1104 ofthe edge device 1204 or from the cloud building graph 1102 of the twinmanager 108 or an edge building graph of another edge device. Similarly,the twin manager 108 could receive information from the cloud buildinggraph 1102 and/or the edge building graph 1104 of the edge device 1204.

In step 1606, the system can perform one or more operations on theinformation received in the step 1604 to derive an output and ingest theoutput into the building graph (e.g., the building graph 1102 or theedge building graph 1104). The derived information can be displayed inthe user device 176 for review by a user, and/or use the information tooperate building systems of the building, e.g., the building subsystems122, to control environmental conditions of a building, e.g.,temperature, pressure, humidity, air quality, light, etc..

Referring now to FIG. 17 , a process 1700 where the distributed buildinggraph 1100 is generated across the twin manager 108 and an edge device1204 during onboarding is shown, according to an exemplary embodiment.The process 1700 can be performed by the edge device 1204 and the twinmanager 108. The process 1700 can be performed by one or more edgesystems and/or one or more cloud systems. Furthermore, any computingdevice described herein can be configured to perform the process 1700.

In step 1702, the edge device 1204 can receive metadata from one or moredevices connected to the edge device 1204. For example, the metadata maybe self-describing information of the one or more devices, e.g., devicename, device purpose, device network identifier, device space location,sensor points, actuator points, units, data produced, etc. In someembodiments, the edge device 1204 receives, via the onboarding tool1304, metadata from the AHU controller 1322 describing the AHUcontroller 1322 and/or the AHU sensors 1324 and/or the AHU actuators1326 that are connected to (and/or controlled by) the AHU controller1322. Similarly, in some embodiments, the edge device 1204 receives, viathe onboarding tool 1304, metadata from the VAV1-2 controller 1316describing the VAV1-2 controller 1316 and/or the VAV sensors 1318 and/orthe VAV actuators 1320 that are connected to (and/or controlled by) theVAV1-2 controller 1316.

In step 1704, the edge device 1204 (e.g., via the onboarding tool 1304)generates a first building graph, e.g., the edge building graph 1104,which includes multiple nodes representing entities of the buildingincluding the one or more devices for which metadata is received in thestep 1702. The graph can further include edges that indicates therelationships between the entities. For example, based on the metadatareceived for the AHU controller 1322 (e.g., an identifier “AHU1”) andthe metadata received for the VAV1-2 controller 1316 (e.g., anidentifier “VAV1-2”), the onboarding tool 1304 could generate therespective the AHU1 node 1128 representing the AHU controlled by the AHUcontroller 1322 and the VAV1-2 node 1130 representing the VAV controlledby the VAV1-2 controller 1316.

Furthermore, the metadata received from the AHU controller 1322 and/orthe VAV1-2 controller 1316 could indicate that the AHU1 feeds the VAV1-2air. This could be identified though an explicit indication that theVAV1-2 receives air from the AHU1, though an identification ofparameters controlled by the AHU controller affecting measurements ofthe VAV1-2, indications of network connections between the AHUcontroller 1322 and/or VAV1-2 controller 1316 indicating a controlrelationship, etc. The indication of the relationship can be used by theonboarding tool 1304 to generate the feeds edge 1170 linking the AHU1node 1128 and the VAV1-2 node 1130. The onboarding tool 1304 couldfurther receive a location tag from the VAV1-2 controller 1316. Thelocation tag could indicate “zone1-2” or any other location name, e.g.,“Main Lobby,” “Bob's Office,” “Family Room,” etc. The location tag may,in some embodiments, be programmed by a user for the VAV1-2 controller1316 when the VAV1-2 controller 1316 is first installed. The onboardingtool 1304 can generate the zone1-2 node 1132 for the location of theVAV1-2 and generate a feeds edge 1172 between the VAV1-2 node 1130 andthe zone1-2 node 1132 based on the indication that the VAV1-2 isinstalled in the zone1-2.

In some embodiments, the edge agents 1208 may execute operations againstthe edge building graph 1104. The results of the edge agents 1208 can,in some embodiments, be used by the edge agents 1208 and/or theonboarding tool 1304 to generate a node for the inferences produced bythe edge agents 1208. For example, if the edge agents 1208 deriveinformation for the AHU1, the edge device 1204 can cause the edgebuilding graph 1104 to include an AI inference event stream node 1134and an edge 1174 between the AHU1 node 1128 and the node 1134.

In step 1706, the edge device 1204 can receive, from a cloud system oranother edge system, indications of second entities and secondrelationships between the entities and the second entities. The cloudsystem or another edge system may store a second building graph storinga plurality of second nodes representing the second entities and secondedges between the second plurality of nodes representing relationshipsbetween the second entities. In some embodiments, the second buildinggraph is generated in a similar manner as described in steps 1702-1704by the cloud system or the other edge system. In step 1708, the edgedevice 1204 can generate one or more nodes or edges linking the firstbuilding graph to the second building graph, the one or more nodes oredges relating the entities and the second entities.

In some embodiments, the edge device 1204 the onboarding tool 1304 ofthe edge device 1204 may receive an indication of, or data of, the cloudbuilding graph 1102 from the twin manager 108. The onboarding tool 1304can use the received data from the twin manager 108 to generate the node1126 and/or the edges 1162-1168. For example, in some embodiments, aname or other indicator of the cloud building graph 1102 received fromthe twin manager 108 can be used by the edge device 1204 to generate thecloud1 node 1126 representing the cloud building graph 1102.Furthermore, the data received by the edge device 1204 from the twinmanager 108 can indicate relationships between the nodes stored by theedge building graph 1104 and the nodes stored by the cloud buildinggraph 1102.

For example, the edge device 1204 may receive an indication of a“VAV1-1” represented as a node in the cloud building graph 1102.Furthermore, the edge device 1204 can receive an indication that the“VAV1-1” is fed by the AHU1 which is represented in the cloud buildinggraph 1102. Responsive to receiving this data, the edge device 1204 cangenerate the edge 1162 between the AHU1 node 1128 and the cloud1 node1126. Furthermore, the edge device 1204 could receive indications thattwo floors, floor 1 and floor 2 are also fed by the AHU1. Responsive toreceiving this data, the edge device 1204 can generate the edges 1166and 1162 between the AHU1 node 1128 and the cloud1 node 1126. In someembodiments, the edge device 1204 can receive an indication that thecloud building graph 1102 includes a node that describes a floor thatthe zone1-2 represented by the zone1-2 node 1132 is a part of.Responsive to receiving this data, the edge device 1204 can generate theedge 1168 between the cloud1 node 1126 and the zone1-2 node 1132.

In some embodiments, a single system or device (e.g., the twin manager108 and/or the edge device 1204) could receive metadata from a varietyof data sources, e.g., directly or indirectly from controllers, sensors,actuators, from one or more databases, from a user device, etc. Thesystem can identify one or more edge systems or cloud systems thatinclude processing resources (e.g., memory availability, storageavailability, processing speed, number of processor cores, etc.)necessary to store and run a digital twin (e.g., a building graph and/orone or more agents). The system can construct multiple building graphswith interconnections. The system can communicate, via the network 104,the building graphs to the one or more edge systems and/or cloudsystems. In some embodiments, the twin manager 108 can construct thevarious graphs and push the graphs to the various edge devices. In someembodiments, the twin manager 108 may retain nodes or edges in the cloudthat are linked to the nodes and/or edges of the graphs of the variousedge devices.

In some embodiments, a user may construct a digital twin via the userdevice 176. In some embodiments, the user may provide input to the twinmanager 108, the user input defining one or multiple different graphsvia the user device 176. The user input can, in some embodiments, definethe nodes and/or edges of each graph and interconnections between thegraphs. The user input may further provide an assignment of each graphto a particular system, e.g., edge system, cloud system, etc. The twinmanager 108, responsive to receiving a user command, push the graphs tothe various edge systems and/or cloud systems. Examples of constructinga graph via user input is described in U.S. patent application Ser. No.16/723,087, filed Dec. 20, 2019 and U.S. patent application Ser. No.16/175,507 filed Oct. 30 2018, the entireties of which are incorporatedby reference herein.

CONFIGURATION OF EXEMPLARY EMBODIMENTS

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements may bereversed or otherwise varied and the nature or number of discreteelements or positions may be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepsmay be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions may be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Wheninformation is transferred or provided over a network or anothercommunications connection (either hardwired, wireless, or a combinationof hardwired or wireless) to a machine, the machine properly views theconnection as a machine-readable medium. Thus, any such connection isproperly termed a machine-readable medium. Combinations of the above arealso included within the scope of machine-readable media.Machine-executable instructions include, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing machines to perform a certain function orgroup of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps maybe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

In various implementations, the steps and operations described hereinmay be performed on one processor or in a combination of two or moreprocessors. For example, in some implementations, the various operationscould be performed in a central server or set of central serversconfigured to receive data from one or more devices (e.g., edgecomputing devices/controllers) and perform the operations. In someimplementations, the operations may be performed by one or more localcontrollers or computing devices (e.g., edge devices), such ascontrollers dedicated to and/or located within a particular building orportion of a building. In some implementations, the operations may beperformed by a combination of one or more central or offsite computingdevices/servers and one or more local controllers/computing devices. Allsuch implementations are contemplated within the scope of the presentdisclosure. Further, unless otherwise indicated, when the presentdisclosure refers to one or more computer-readable storage media and/orone or more controllers, such computer-readable storage media and/or oneor more controllers may be implemented as one or more central servers,one or more local controllers or computing devices (e.g., edge devices),any combination thereof, or any other combination of storage mediaand/or controllers regardless of the location of such devices.

1-20. (canceled)
 21. A method, comprising: receiving, by one or more processing circuits, query data to query a first digital twin of a building, the first digital twin comprising: a plurality of first entities of a plurality of entities of the building and a plurality of first relationships of a plurality of relationships, the plurality of first relationships between the plurality of first entities; and a relationship between a first entity of the plurality of first entities stored within the first digital twin and a second entity of a plurality of second entities of the plurality of entities stored within a second digital twin, the second digital twin comprising the plurality of second entities of the plurality of entities and a plurality of second relationships of the plurality of relationships between the plurality of second entities; identifying, by the one or more processing circuits, that a query result for the query data is stored in the second digital twin based on the relationship of the first digital twin; receiving, by the one or more processing circuits, the query result from the second digital twin; and performing, by the one or more processing circuits, one or more operations based on the query result.
 22. The method of claim 21, comprising: identifying, by the one or more processing circuits, a particular system that stores the second digital twin based on a lookup table, wherein the lookup table stores a plurality of indications of digital twins including the first digital twin and the second digital twin and links between the digital twins and systems that store the digital twins.
 23. The method of claim 21, comprising: identifying, by a processing circuit of a first system, a communication issue between the first system storing the first digital twin and a second system storing the second digital twin; and performing, by the processing circuit, the one or more operations based on data determined based on the first digital twin.
 24. The method of claim 21, comprising: executing, by the one or more processing circuits, an agent to: perform the one or more operations based on the first digital twin; and ingest a result of the one or more operations into the first digital twin.
 25. The method of claim 21, wherein: the second digital twin includes a second relationship that forms a connection between the second digital twin and the first digital twin by linking the second entity of the plurality of second entities of the second digital twin and the first entity of the plurality of first entities of the first digital twin.
 26. The method of claim 21, wherein: the first digital twin includes a first graph structure including a plurality of first nodes representing the plurality of first entities and a plurality of first edges between the plurality of first nodes representing the plurality of first relationships between the plurality of first entities; and the second digital twin includes a second graph structure including a plurality of second nodes representing the plurality of second entities and a plurality of second edges between the plurality of second nodes representing the plurality of second relationships between the plurality of second entities.
 27. The method of claim 26, wherein: the first graph structure includes a node identifying the second graph structure; and the first graph structure includes an edge between a first node of the plurality of first nodes representing the first entity and the node identifying the second graph structure, wherein the edge represents the relationship between the first entity of the plurality of first entities of the first digital twin and the second entity of the plurality of second entities of the second digital twin.
 28. The method of claim 27, wherein the edge includes data including: a first indication of the first entity; a second indication that the first entity is stored by the first graph structure; a third indication of the second entity; a fourth indication that the second entity is stored by the second graph structure; and a fifth indication of a relationship type of a plurality of relationship types describing the relationship between the first entity of the plurality of first entities of the first digital twin and the second entity of the plurality of second entities of the second digital twin.
 29. The method of claim 21, comprising: receiving, by the one or more processing circuits, at least a portion of building data describing the plurality of entities of the building and the plurality of relationships between the plurality of entities, the plurality of entities represent at least one of a device, a space, the building, a point, or a person; and generating, by the one or more processing circuits, the first digital twin based on the building data, wherein a first system stores the first digital twin and a second system stores the second digital twin generated based on the building data.
 30. The method of claim 29, comprising: querying, by a processing circuit of a first system, the first digital twin based on the query data, the one or more processing circuits comprising the processing circuit of the first system; identifying, by the processing circuit of the first system, that the query result of the query is stored in the second digital twin based on the relationship; communicating, by the processing circuit of the first system, the query to a second system; receiving, by the processing circuit of the first system, the query result from the second system; and performing, by the processing circuit of the first system, the one or more operations based on the query result.
 31. The method of claim 30, wherein: the first system comprises a cloud system stored off premises from the building; and the second system comprises an edge system stored on a premises of the building.
 32. The method of claim 30, comprising: performing, by the one or more processing circuits, an onboarding to generate the first digital twin and the second digital twin by: receiving, by the processing circuit of the first system, first building data; generating, by the processing circuit of the first system, the first digital twin based on the first building data; receiving, by a second processing circuit of the second system, second building data; generating, by the second processing circuit of the second system, the second digital twin based on the second building data; identifying, by the processing circuit of the first system, the relationship by communicating with the second system; and causing, by the processing circuit of the first system, the first digital twin to include the relationship.
 33. The method of claim 30, comprising: receiving, by a second processing circuit of the second system, the query data from the processing circuit of the first system; querying, by the second processing circuit of the second system, the second digital twin with the query data to generate the query result; and transmitting, by the second processing circuit of the first system, the query result to the processing circuit of the first system.
 34. A building system, comprising: one or more memory devices storing instructions thereon that, when executed by one or more processors, cause the one or more processors to: receive query data to query a first digital twin of a building, the first digital twin comprising: a plurality of first entities of a plurality of entities of the building and a plurality of first relationships of a plurality of relationships, the plurality of first relationships between the plurality of first entities; and a relationship between a first entity of the plurality of first entities stored within the first digital twin and a second entity of a plurality of second entities of the plurality of entities stored within a second digital twin, the second digital twin comprising the plurality of second entities of the plurality of entities and a plurality of second relationships of the plurality of relationships between the plurality of second entities; identify that a query result for the query data is stored in the second digital twin based on the relationship of the first digital twin; receive the query result from the second digital twin; and perform one or more operations based on the query result.
 35. The building system of claim 34, wherein: the first digital twin includes a first graph structure including a plurality of first nodes representing the plurality of first entities and a plurality of first edges between the plurality of first nodes representing the plurality of first relationships between the plurality of first entities; and the second digital twin includes a second graph structure including a plurality of second nodes representing the plurality of second entities and a plurality of second edges between the plurality of second nodes representing the plurality of second relationships between the plurality of second entities.
 36. The building system of claim 35, wherein: the first graph structure includes a node identifying the second graph structure; and the first graph structure includes an edge between a first node of the plurality of first nodes representing the first entity and the node identifying the second graph structure, wherein the edge represents the relationship between the first entity of the plurality of first entities of the first digital twin and the second entity of the plurality of second entities of the second digital twin.
 37. The building system of claim 36, wherein the edge includes data including: a first indication of the first entity; a second indication that the first entity is stored by the first graph structure; a third indication of the second entity; a fourth indication that the second entity is stored by the second graph structure; and a fifth indication of a relationship type of a plurality of relationship types describing the relationship between the first entity of the plurality of first entities of the first digital twin and the second entity of the plurality of second entities of the second digital twin.
 38. One or more storage medium storing instructions thereon, that, when executed by one or more processors, cause the one or more processors to: receive query data to query a first digital twin of a building, the first digital twin comprising: a plurality of first entities of a plurality of entities of the building and a plurality of first relationships of a plurality of relationships, the plurality of first relationships between the plurality of first entities; and a relationship between a first entity of the plurality of first entities stored within the first digital twin and a second entity of a plurality of second entities of the plurality of entities stored within a second digital twin, the second digital twin comprising the plurality of second entities of the plurality of entities and a plurality of second relationships of the plurality of relationships between the plurality of second entities; identify that a query result for the query data is stored in the second digital twin based on the relationship of the first digital twin; receive the query result from the second digital twin; and perform one or more operations based on the query result.
 39. The one or more storage medium of claim 38, comprising: perform an onboarding to generate the first digital twin and the second digital twin by: receiving first building data; generating the first digital twin based on the first building data; receiving second building data; generating the second digital twin based on the second building data; identifying the relationship; and causing the first digital twin to include the relationship.
 40. The one or more storage medium of claim 38, wherein: the first digital twin includes a first graph structure including a plurality of first nodes representing the plurality of first entities and a plurality of first edges between the plurality of first nodes representing the plurality of first relationships between the plurality of first entities; and the second digital twin includes a second graph structure including a plurality of second nodes representing the plurality of second entities and a plurality of second edges between the plurality of second nodes representing the plurality of second relationships between the plurality of second entities. 